issues
search
tmandry
/
lavender
Generate Visual Studio projects for Bazel (experimental)
MIT License
73
stars
17
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
How to resolve: unknown repo 'bazel-msbuild' requested from @@
#20
av-emogai
opened
6 months ago
0
Pass `--config` to the `bazel build` invocation
#19
werat
opened
2 years ago
0
I want to turn this project into a solution project using lavender but unfortunately it gives me this error every time I run it.
#18
rigngsbase
opened
2 years ago
1
[WinError 206] The filename or extension is too long
#17
NuncObdurat
opened
2 years ago
0
Ensure the output directory exists even if a label contains slashes
#16
lummax
closed
1 year ago
0
Lookup the `bazel` binary from the `BAZEL` environment variable
#15
lummax
closed
1 year ago
0
Make it output sane visual studio project names, and use VS2019.
#14
tvandijck
opened
3 years ago
0
Fix Starlark errors for Bazel 0.28.0
#13
laszlocsomor
closed
5 years ago
2
One or more projects in the solution were not loaded correctly
#12
Vertexwahn
opened
5 years ago
0
Quote bazel executable path in vcxproj
#11
plule
closed
5 years ago
1
Error: Information about the C++ toolchain API is not accessible anymore through ctx.fragments.cpp
#10
plule
opened
5 years ago
4
Pick the toolset automatically
#9
tmandry
opened
6 years ago
0
Add acceptance/regression testing
#8
tmandry
opened
6 years ago
0
Decide on how to handle targets from other languages like Python
#7
tmandry
opened
6 years ago
0
Use solution folders to organize projects
#6
tmandry
opened
6 years ago
0
Debugger, error messages go to file in bazel exec_root
#5
tmandry
opened
6 years ago
0
Use exec_root paths for source files
#4
tmandry
opened
6 years ago
0
cc_library with no src files causes error in Visual Studio
#3
tmandry
opened
6 years ago
0
Blakefiler
#2
jart
closed
6 years ago
3
mentioning bazel-msbuild in the Bazel newsletter for Bazel 0.12.0?
#1
laszlocsomor
closed
6 years ago
7