You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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?
Beta Was this translation helpful? Give feedback.
All reactions