configure-vscode-for-bazel
If you want to work with C++ Bazel targets in VS Code, you can use configure-vscode-for-bazel to generate a VS Code configuration.
This tool supports generating:
.vscode/launch.jsonandtasks.jsonfiles that contain selected targets for debugging and compiling in VS Code and- a
compile_commands.jsonfile using bazel-compile-commands-extractor for selected targets.
To generate these for a defined set of targets, run
uvx configure-vscode-for-bazel //path/to/your/target/...
This will be forwarded to a bazel query listing all cc_binary and cc_test targets.
Then, when you go to VSCode -> Run and Debug (Ctrl+Shift+D) you'll be able to select an executable.
By pressing ▶ Start Debugging (F5), you'll trigger a bazel build command and start debugging the executable.
The latter is provided by C/C++ Microsoft extension.
Make sure you compile with debug symbols (--compilation_mode=dbg) enabled.
You can pass your Bazel flags to this tool with --additional-debug-arg.
In addition, a .vscode/BUILD.bazel file will be created and bazel-compile-commands-**extractor** run to create a compile_commands.json in the workspace root.
See the usage documentation for more information.
1 maintainer
Metadata
1 maintainer
Release files for configure-vscode-for-bazel 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| configure_vscode_for_bazel-0.3.0.tar.gz | 5.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| configure_vscode_for_bazel-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.3 kB
Release files / configure_vscode_for_bazel-0.3.0.tar.gz
| Download URL | configure_vscode_for_bazel-0.3.0.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f2bfaba5ea00d5bfe4a70bcc791685492b1bda9d5fe9fa848dcc4298136fc4c2
|
|
BLAKE2b-256 checksum How to use checksums |
a8f4fb65746220571a71ffbe8d9158f8ee248ab1fcb2dfe4e43ec180291fd577
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 31, 2026.
Transparency logRelease files / configure_vscode_for_bazel-0.3.0-py3-none-any.whl
| Download URL | configure_vscode_for_bazel-0.3.0-py3-none-any.whl |
|---|---|
| Size | 6.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e50e6460dcfe9054e3c8f74f7975b7d8ad5837f76506d278d7743e87c1b2754c
|
|
BLAKE2b-256 checksum How to use checksums |
861aff32567fcd9d8d42a32fc41b7e2ab7df5387c926f19998b490dd6a4f26c8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 31, 2026.
Transparency log
