Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[boost-python] Feature to install pip/numpy for vcpkg installed python installation #34565

Closed
SPKorhonen opened this issue Oct 18, 2023 · 3 comments
Assignees
Labels
category:port-feature The issue is with a library, which is requesting new capabilities that didn’t exist Stale

Comments

@SPKorhonen
Copy link

Is your feature request related to a problem? Please describe.

Currently boost-python build process pulls the numpy required to build boost-python the wrappers for numpy from external python installation which could incompatibilities.

Proposed solution

One could add a feature "numpy" to boost-python which would use the vcpkg installed python to install pip via ensurepip and subsequently to install numpy via pip which can then be used to build boost-python.

By default we could install either latest version of numpy or a specific hard-coded version. There could also be an environmental variable like VCPKG_NUMPY_VERSION which can be used to specify the desired version.

I have implemented this in a fork of vcpkg and could submit a PR.

Describe alternatives you've considered

The current work-around is to keep a compatible version of python and numpy so that the jam build system finds the required numpy installation from external source outside of vcpkg.

Additional context

No response

@SPKorhonen SPKorhonen added the category:port-feature The issue is with a library, which is requesting new capabilities that didn’t exist label Oct 18, 2023
@Neumann-A
Copy link
Contributor

I have an overlay for numpy: https://github.com/Neumann-A/my-vcpkg-ports/tree/master/numpy but you also need an overlay for boost pulling in it.

Copy link

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 180 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.

@github-actions github-actions bot added the Stale label Apr 16, 2024
@jimwang118 jimwang118 removed the Stale label Apr 16, 2024
@aminya aminya mentioned this issue May 21, 2024
5 tasks
Copy link

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 180 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.

@github-actions github-actions bot added the Stale label Oct 14, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-feature The issue is with a library, which is requesting new capabilities that didn’t exist Stale
Projects
None yet
Development

No branches or pull requests

3 participants