# Cmake meets setuptools
## Try the example
The example module foo contains the methods add and inverse. The inverse method is part of an external C/C++ library against which is linked after module compilation.
### Build the example module `bash cd example `
`bash python3 setup.py bdist_wheel # build as wheel python3 setup.py build_ext -i # build in-place `
### Test the example module `bash python3 -c "import foo; print(foo.inverse(0.5))" `
This should compile the static library deadbeef, compile the foo.bar submodule and print 2.0 upon execution.
1 maintainer
Metadata
1 maintainer
Release files for setuptools-cmake 1.1
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 | |
|---|---|---|---|---|
| setuptools-cmake-1.1.tar.gz | 3.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| setuptools_cmake-1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.5 kB
Release files / setuptools-cmake-1.1.tar.gz
| Download URL | setuptools-cmake-1.1.tar.gz |
|---|---|
| Size | 3.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
df951bff7c407c876e0ec15e751604d4c8736fdec50919c90e184b0db9d7b970
|
|
BLAKE2b-256 checksum How to use checksums |
49c40d4c103c1b28b7ca95e5bf89dc18f38fc5884cc74cef6ea2810b769030da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Release files / setuptools_cmake-1.1-py3-none-any.whl
| Download URL | setuptools_cmake-1.1-py3-none-any.whl |
|---|---|
| Size | 4.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ade0eeb33d5e9e94437a7a3261596ac76af4d9d3bc5842085e9b69ae1a70f5d8
|
|
BLAKE2b-256 checksum How to use checksums |
29311227e445d56e69d15bad3ac24502f1d628bc32c3b4cc14df11632e122475
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Security for setuptools-cmake 1.1
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.
