Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Survey of Python build backends handling non-Python software #4

Open
6 tasks
sethmlarson opened this issue Nov 4, 2024 · 1 comment
Open
6 tasks
Assignees

Comments

@sethmlarson
Copy link
Member

sethmlarson commented Nov 4, 2024

These build backends are likely to have a more complicated use-case, such as needing to generate their own SBOMs instead of only forwarding along SBOM documents specified in pyproject.toml.

  • Maturin and PyO3
  • setuptools
  • Meson-build
  • enscons
  • cmake
  • scikit-build
@sethmlarson sethmlarson self-assigned this Nov 4, 2024
@ncoghlan
Copy link

ncoghlan commented Nov 5, 2024

Additional "full fledged build systems that can emit Python packages" options:

There are also projects like zig and compiletools, as well as Rust, where non-Python dependencies may end up statically linked into the resulting extension modules.

There probably needs to be a way to just inject additional SBOM snippets directly, and leave it up to the project itself to manage keeping them in sync with the actual build process. Defining a common way to do that would mean that each affected build system project didn't need to invent one for itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants