dogebuild-c
C language plugin for dogebuild
Install dogebuild c plugin
Install dogebuild c plugin via pip:
pip install dogebuild-c
Dogebuild will be installed as a dependency.
Creating project with tapas
The easiest way to create project is to use tapas scaffold tool. To install tapas use pip:
pip install tapas
And then run tapas and follow instructions:
tapas dogebuild-c <target-dir>
Manually creating project
Create dogefile.py and fill it with following code:
from pathlib import Path
from dogebuild_c.c_plugin import CPlugin, BinaryType
CPlugin(
binary_type=BinaryType.EXECUTABLE,
out_name="executable_name",
src=Path("src").glob('**/*.c'),
headers=Path("src").glob('**/*.h'),
)
Create directory src and put all your source code files into that.
Building project
To build project run dogebuild in project directory:
doge build
To build and run project run:
doge run
Next steps
Advanced documentation for dogebuild available in readthedocs.
Advanced documentation for dogebuild c plugin available in readthedocs.
Metadata
Release files for dogebuild-c 0.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 | Actions |
|---|---|---|---|---|
| dogebuild-c-0.1.1.tar.gz | 4.8 kB | Without provenance | Details for dogebuild-c-0.1.1.tar.gz |
Release files / dogebuild-c-0.1.1.tar.gz
| Download URL | dogebuild-c-0.1.1.tar.gz |
|---|---|
| Size | 4.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
407ac9c224405e33700f13005e730fd65f8ef70742d18083af1f9e4a3baa30ab
|
|
BLAKE2b-256 checksum How to use checksums |
f54a0c074c1d289f5b01f2efa07fcd5666a6999304496b39e05bbda5c227bd7f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.1.0 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.7.1
|
Security for dogebuild-c 0.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.