dev-pipeline-cmake
A CMake plugin for dev-pipeline
Installation
The simplest way to install is using pip.
$ cd /path/to/dev-pipeline-cmake
$ pip3 installIf you don’t have pip available, you can run setup.py directly.
$ cd /path/to/dev-pipeline-cmake
$ python3 setup.py installYou’ll need cmake installed. Doing that is beyond the scope of this document, but it should be available for pretty much every operating system.
Using
You can use cmake as an option for build in a
build.config. Information about options you can set are in the
documentation.
1 maintainer
Metadata
1 maintainer
Release files for dev-pipeline-cmake 0.4.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 | Actions |
|---|---|---|---|---|
| dev-pipeline-cmake-0.4.1.tar.gz | 3.9 kB | Without provenance | Details for dev-pipeline-cmake-0.4.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dev_pipeline_cmake-0.4.1-py3-none-any.whl | Python 3 | none | any | Details for dev_pipeline_cmake-0.4.1-py3-none-any.whl |
Total release size: 9.9 kB
Release files / dev-pipeline-cmake-0.4.1.tar.gz
| Download URL | dev-pipeline-cmake-0.4.1.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
089c8acfb0b797cd4592e1c8d43e7d1758c5a5da7dab7e267989767602fee93b
|
|
BLAKE2b-256 checksum How to use checksums |
c43af22cb4ad430bd65a31d02bdb80900a304c8f86c7165e1d2ac3314e585c57
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.18.4 setuptools/36.7.2 requests-toolbelt/0.8.0 tqdm/4.23.3 CPython/3.6.5
|
Release files / dev_pipeline_cmake-0.4.1-py3-none-any.whl
| Download URL | dev_pipeline_cmake-0.4.1-py3-none-any.whl |
|---|---|
| Size | 6.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0e1ab01cc71c1643fce37b4cc4ae0bfb89436baa90867f7c7d5ec97ea84227ae
|
|
BLAKE2b-256 checksum How to use checksums |
eccbb10c0ec6369142c60ee99210cfc8905cac42a1047fe36b50329474bcbe70
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.18.4 setuptools/36.7.2 requests-toolbelt/0.8.0 tqdm/4.23.3 CPython/3.6.5
|
Security for dev-pipeline-cmake 0.4.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.
