Skip to content

Conversation

@yoonghm
Copy link

@yoonghm yoonghm commented Aug 19, 2019

The original code use python -c "import sys; print(sys.prefix)" which did not show actual directory for include file.

The proper way is python -c "from sysconfig import get_paths as gp; print(gp()['include'])"

@ali5h
Copy link

ali5h commented Aug 25, 2019

with this patch i see the change in project-config.jam but g++ calls still use the wrong include path for python include.

@mclow
Copy link
Contributor

mclow commented Aug 28, 2019

A nit: We don't take PRs against the master branch. We take them against develop, then let the tests run, and merge to master.

@jsharpe
Copy link

jsharpe commented Dec 3, 2019

This patch is incorrect - the real issue looks to be in boost build - if you don't fully specify version, includes and libraries in the python script it ignores the given version and tries to infer it from sys.version which is missing the m part of the version string.

@jsharpe
Copy link

jsharpe commented Dec 3, 2019

See boostorg/build#481

@likan999
Copy link

I don't see how this could solve the problem. The issue is python.jam that sets the path to $(prefix)/include/python$(version).

Copy link
Contributor

@Flamefire Flamefire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code looks correct as-is: $PYTHON_ROOT gets set to the root of the Python install, so this PR would set it to a wrong value

@yoonghm yoonghm closed this by deleting the head repository Dec 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants