Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/tmandry/lavender
Generate Visual Studio projects for Bazel (experimental)
https://github.com/tmandry/lavender
bazel visual-studio
Last synced: about 2 months ago
JSON representation
Generate Visual Studio projects for Bazel (experimental)
- Host: GitHub
- URL: https://github.com/tmandry/lavender
- Owner: tmandry
- License: mit
- Created: 2018-02-28T17:16:22.000Z (almost 7 years ago)
- Default Branch: master
- Last Pushed: 2022-05-23T14:13:37.000Z (over 2 years ago)
- Last Synced: 2024-10-14T11:52:33.408Z (about 2 months ago)
- Topics: bazel, visual-studio
- Language: Python
- Homepage:
- Size: 42 KB
- Stars: 75
- Watchers: 6
- Forks: 17
- Open Issues: 14
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-bazel - Lavender - Generate Visual Studio projects that uses Bazel for the actual building (Tooling / Project generators)
README
# Lavender
Generate Visual Studio projects with bazel. The projects use bazel to do the actual building.
Currently this only works for C++. Support for building targets in other languages is planned.
Formerly bazel-msbuild.
## Prerequistes
- bazel
- Python 2 or 3
## Getting started
Run this in your normal development environment (MSYS bash, cmd.exe, or PowerShell):
```
$ git clone https://github.com/tmandry/lavender.git
# Then, in your bazel project...
$ python /path/to/lavender/generate.py //mypackage/...
$ start msbuild/myproject.sln
```
Where `//mypackage/...` is an optional Bazel query describing which packages you want to generate projects for. Generally, you want to use a package name, label name, or wildcard such as `//mypackage/...`, which means "mypackage and everything beneath it".
You can specify more than one query. If you specify no query, projects will be generated for ALL packages. Be careful on large repos!
### Environment
The environment you start Visual Studio from affects how Bazel is configured. Make sure this environment is configured according to the [Using Bazel on Windows](https://docs.bazel.build/versions/master/windows.html) docs; in particular, it's important to set `BAZEL_SH` system-wide. If your environment settings are different between Visual Studio and your terminal, you might end up talking to two different Bazel servers.
### Debugging
Full C++ debugging is supported.
However, when debugging, Visual Studio will open up source file names built into the binary that are symlinks to the original source. This can be confusing, because you will have two copies of the same file open. Making a change to one may cause Visual Studio to prompt you about changes made to the other tab. It is best to check "Always reload files when there are no unsaved changes", so that this becomes less annoying.
## Name
Lavender is the [color of the Visual Studio logo](https://en.wikipedia.org/wiki/Microsoft_Visual_Studio). It's also an herb, like basil.
## Usage
```
usage: generate.py [-h] [--output OUTPUT] [--solution SOLUTION]
[--config CONFIG]
[query [query ...]]
Generates Visual Studio project files from Bazel projects.
positional arguments:
query Target query to generate project for [default: all
targets]
optional arguments:
-h, --help show this help message and exit
--output OUTPUT, -o OUTPUT
Output directory
--solution SOLUTION, -n SOLUTION
Solution name [default: current directory name]
--config CONFIG Additional --config option to pass to bazel; may be
used multiple times
```
## Related projects
- [vscode-bazel-tools](https://github.com/dprogm/vscode-bazel-tools): Integration with Visual Studio Code
- [Blakefiler](https://gist.github.com/jart/082b1078a065b79949508bbe1b7d8ef0): Generates a Makefile to build bazel targets for distribution