pybind / pybind/pybind11

[BUG]: Missing runtime dlls in Windows

Open
#3,396 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

triage
Dominant language
C++
Stars
18k
Forks
2.3k
Avg merge
5d 17h
Merged PRs (30d)
10

Description

Required prerequisites
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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.