ccbuilder can build and install llvm and gcc.
Basic Usage:
ccbuilder build [compiler] [revision]
compiler must be either llvm or gcc and revision either a commit hash
or a tag.
ccbuilder relies on clones the GCC and LLVM git repos and can build most of their recent revisions/commits/tags, e.g.,
ccbuilder build gcc releases/gcc-13.1.0 will build GCC 13.1.0.
The built compilers are installed under ccbuilder's compiler store (a filesystem directory).
After building a compiler, its installation location is printed, e.g.:
% ccbuilder build llvm main
/path/to/ccbuilder_compiler_store/clang-ff7d2fabe074d95cefb683d4a742eec172bd36d5
% /path/to/ccbuilder_compiler_store/clang-ff7d2fabe074d95cefb683d4a742eec172bd36d5/bin/clang -v
clang version 18.0.0 (https://github.com/llvm/llvm-project.git ff7d2fabe074d95cefb683d4a742eec172bd36d5)
...
ccbuilder stores everything under $HOME/.cache, the default locations can
be overriden via command line flags, e.g., ccbuilder build llvm master --compiler-store-path /some/other/path
To update the compiler git repos use ccbuilder --pull.
For more options check ccbuilder -h.
Installation:
pip install [-U] ccbuilder
Metadata
Release files for ccbuilder 0.1.2
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 |
|---|---|---|---|---|
| ccbuilder-0.1.2.tar.gz | 100.0 kB | Without provenance | Details for ccbuilder-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ccbuilder-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for ccbuilder-0.1.2-py3-none-any.whl |
Total release size: 209.0 kB
Release files / ccbuilder-0.1.2.tar.gz
| Download URL | ccbuilder-0.1.2.tar.gz |
|---|---|
| Size | 100.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
59467850ee82cc4d0e9b3a5049de9ec5fb4787099989bcf51fd8e6e32bd522b8
|
|
BLAKE2b-256 checksum How to use checksums |
ee4d7d95be1a22cb85e4abe18a68bbb05e6657bee665925cef3ccc65612cbee1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Release files / ccbuilder-0.1.2-py3-none-any.whl
| Download URL | ccbuilder-0.1.2-py3-none-any.whl |
|---|---|
| Size | 109.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
519e5fa085c024c8988b8e0df2f4507ea79ef71025000b41f1101daa8841cc97
|
|
BLAKE2b-256 checksum How to use checksums |
fcdfdf87b38126147c7c424c15d23f0c7dc72444a36319d2b47bd8f4df08f5e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Security for ccbuilder 0.1.2
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.