Headers as Dependencies
HaD reads the #included headers from a bunch of C files and prints the corresponding compiler options.
For instance, if #include <math.h> is used, option -lm is required, or if #include <pthread.h> is used, -pthread is required.
To do so, HaD relies on a database maintained by hand, as well as on pkg-config.
It currently supports only GCC and Clang on Linux.
Contributions welcome!
You can help a lot by enriching files hadlib/*.cfg.
This is actually the heart of the tool.
All the rest is simple code to read and present this knowledge.
Licence
HaD is published as free software under the terms of the MIT licence
Metadata
Release files for Headers-as-Dependencies 0.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 |
|---|---|---|---|---|
| Headers as Dependencies-0.3.tar.gz | 6.0 kB | Without provenance | Details for Headers as Dependencies-0.3.tar.gz |
Release files / Headers as Dependencies-0.3.tar.gz
| Download URL | Headers as Dependencies-0.3.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4a4b9d0c1e664b263c466cc88ba5130c04835ff341972f8ec53cb0551453a4ff
|
|
BLAKE2b-256 checksum How to use checksums |
d8bfa215af55ef02a0dad82db41d259eb0056e0fa1a1094375cd81c05611a57b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.5.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.8.8
|
Security for Headers-as-Dependencies 0.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.