[BUG]: Missing runtime dlls in Windows
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 18k
- Forks
- 2.3k
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 10
Description
Required prerequisites
- Make sure you've read the documentation. Your issue may be addressed there.
- Search the issue tracker and Discussions to verify that this hasn't already been reported. +1 or comment there if it has.
- Consider asking first in the Gitter chat room or in a Discussion.
Problem description
We are using pybind11 for a project, and we must release the code for this project. Using a default CMAKE setup, the pybind11 dll ends up depending on other dlls, and it isn't immediately clear exactly which ones they are, though they appear to be MSVC runtime libraries. This causes issues, especially on Windows.
Is it possible to link with static versions of these libraries so that the pybind11 dlls don't have (mysterious) dependencies on other dlls that might not be present on another PC? Alternatively, should the pybind11 package load the dlls into the appropriate folder when installed on a Windows machine?
We are using Conda as our package manager.
Reproducible example code
No response
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
No file, test, or entry point is named. Start by reproducing the default CMake setup on Windows with Conda and identifying the runtime DLL dependencies; done would require an agreed solution for preventing or packaging those dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp, python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100