to allow it to introspect the build process to be able to generate a JSON
Compilation Database which can be used with other tools like `clang-tidy`.
## Installation
```shell
$ pip install gcdb
```
## Usage
Run `gcdb` passing in the commands to build your code. You want to ensure the
entire sources are built so its important to clear any prior caches. For
example, if you use `make` to build your code:
```shell
$ gcdb 'make clean && make'
```
NOTE: Currently the passed command cannot run concurrently, so you cannot pass
`-j` to `make or similiar tools.
Home-page: https://github.com/kylef/gcdb
Author: Kyle Fuller
Author-email: kyle@fuller.li
License: UNKNOWN
Description: UNKNOWN
Platform: UNKNOWN
Metadata
Release files for gcdb 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gcdb-0.1.3.tar.gz | 2.0 kB | Without provenance | Details for gcdb-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gcdb-0.1.3-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for gcdb-0.1.3-py2.py3-none-any.whl |
Total release size: 4.5 kB
Release files / gcdb-0.1.3.tar.gz
| Download URL | gcdb-0.1.3.tar.gz |
|---|---|
| Size | 2.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
87370f734cafa189537cb8d54fd3c50161a961a12abe5fc8a4f017565852db6e
|
|
BLAKE2b-256 checksum How to use checksums |
2478b6b5486fb02e77ea12f7334fd67abfcd489a62a273c4ac66a5d51c2df9ed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / gcdb-0.1.3-py2.py3-none-any.whl
| Download URL | gcdb-0.1.3-py2.py3-none-any.whl |
|---|---|
| Size | 2.5 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
66e912abac26f1e51054e20c8b7415db8e558db3bab4acc3b16f2fedeaa9340c
|
|
BLAKE2b-256 checksum How to use checksums |
7ebbb2213292cdf33668d6fa9afc97607590e626354532bcf5032312997cb871
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for gcdb 0.1.3
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.