Python module installed into the bin/ directory instead of the Python module directory
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 5k
- Forks
- 622
- Avg merge
- 8h 37m
- Merged PRs (30d)
- 5
Description
When building with cmake, the Python module installed into the bin/ directory instead of the default Python module directory. I'm not sure, but I think the right way to resolve this is to use the Python3_add_library command from the FindPython3 cmake module. Searching GitHub I found some examples of how to use the Python3_add_library function.
Contributor guide
No contributing guide indexed for this repository
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
Locate the CMake build definition that creates and installs the Python module, then read the FindPython3 documentation and the Python3_add_library examples linked in the issue. Verify the current install destination and confirm the module is installed in the default Python module directory rather than bin/.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp, python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100