brokkr
Build tooling for native C++ libraries shipped as Python wheels (the provider-wheel family: pyyggdrasil, pypddl,
pytyr, pyrunir). A provider wheel bundles its native library, headers and exported CMake package under
<pkg>/native/, and other wheels build and link against it through relative rpaths.
- CMake (
find_package(brokkr)):brokkr_read_project_version(usable beforeproject()),brokkr_find_python_native_prefix,brokkr_register_*,brokkr_python_package_init,brokkr_python_module_rpaths,brokkr_install_native_export,brokkr_install_runtime_path_fixup,brokkr_install_provider_env,brokkr_install_python_stubs,brokkr_install_python_files. - PEP 517 backend (
pybrokkr.build_backend.ProviderBackend): scikit-build-core, with the providers' prefixes put onCMAKE_PREFIX_PATHand the loader path, then the wheel's stubs published and its native libraries stripped.
[build-system]
requires = ["scikit-build-core>=1.0.3,<2", "pybrokkr>=0.1,<0.2", "pyyggdrasil>=0.6,<0.7"]
build-backend = "mypkg_build_backend"
backend-path = ["python"]
# python/mypkg_build_backend.py
from pybrokkr.build_backend import ProviderBackend
ProviderBackend(
package="mypkg",
providers=("pyyggdrasil",),
prefix_defines={"pyyggdrasil": "YGGDRASIL_NATIVE_PREFIX"},
).install_hooks(globals())
cmake_minimum_required(VERSION 3.21)
find_package(brokkr REQUIRED) # wheel builds: found through pybrokkr's cmake.prefix entry point
brokkr_read_project_version(MYPKG_VERSION "${CMAKE_CURRENT_SOURCE_DIR}/pyproject.toml")
project(mypkg VERSION "${MYPKG_VERSION}" LANGUAGES CXX)
In a manual configure, pass -Dbrokkr_DIR="$(python -m pybrokkr --cmake-dir)".
Metadata
Release files for pybrokkr 0.1.0
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 |
|---|---|---|---|---|
| pybrokkr-0.1.0.tar.gz | 34.1 kB | With provenance | Details for pybrokkr-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pybrokkr-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for pybrokkr-0.1.0-py3-none-any.whl |
Total release size: 65.7 kB
Release files / pybrokkr-0.1.0.tar.gz
| Download URL | pybrokkr-0.1.0.tar.gz |
|---|---|
| Size | 34.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
71b575edc379eebffd05830467e5eef5594ce04f4d2fb7534610edda1f272aac
|
|
BLAKE2b-256 checksum How to use checksums |
6ba41c491d354553fb4054be23cce0952f7266a50b2baf07c09ae17dce910387
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / pybrokkr-0.1.0-py3-none-any.whl
| Download URL | pybrokkr-0.1.0-py3-none-any.whl |
|---|---|
| Size | 31.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
34e358a3375b2a090a4984d61a8a151aaa22d6cfb7f5977169acb785a04e3d03
|
|
BLAKE2b-256 checksum How to use checksums |
5e3e0865e2142385d3c568c95524f3c197d2d150c0cdbb469ca2ad4e614e9a0a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logSecurity for pybrokkr 0.1.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pybrokkr-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logA 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.