[Embedding] linking with libpython.a
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 18k
- Forks
- 2.3k
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 10
Description
Is there a means to force pybind11-based projects that embed Python to link with libpython.a (statically) instead of relying on libpython.so?
cc @JohanMabille
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue concerns pybind11-based projects embedding Python and choosing libpython.a instead of libpython.so. Start by examining the embedding and build configuration entry points for how Python libraries are selected. Done means establishing whether static linking can be supported and documenting or implementing the required configuration path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100