Nope, doesn’t help.
However, based on your input, I found install_name_tool and used it to modify
hello_ext.so to point to the actual location. That works well, so at least I
have a path forward with boost.python.
I’m not sure the bjam approach is buying me much compared to Xcode or make, but
On 2019-05-22 2:30 p.m., Jones, Torrin A (US) wrote:
You may need to set PYTHONPATH. Search for PYTHONPATH on this page
for a description.
https://docs.python.org/3/using/cmdline.html
No, PYTHONPATH is used by the Python runtime to locate (Python) modules.
It is not used to resolve shared
On 2019-05-22 2:28 p.m., Andrew Voelkel wrote:
That is helpful. It might indeed be an issue with System Integrity
Protection, now that I do the right google search.
But that leads to the second question. It is possible to indicate
within hello_ext.so where to look for the dylib. Then in the
You may need to set PYTHONPATH. Search for PYTHONPATH on this page for a
description.
https://docs.python.org/3/using/cmdline.html
From: Cplusplus-sig
[mailto:cplusplus-sig-bounces+torrin.jones=baesystems@python.org] On Behalf
Of Andrew Voelkel
Sent: Wednesday, May 22, 2019 10:56 AM
To:
That is helpful. It might indeed be an issue with System Integrity Protection,
now that I do the right google search.
But that leads to the second question. It is possible to indicate within
hello_ext.so where to look for the dylib. Then in theory this wouldn’t a
problem, because I wouldn’t nee
On 2019-05-22 1:55 p.m., Andrew Voelkel wrote:
What magic is the boost environment performing to make this work? What
can I do to make my python extensions look for libboost_python37.dylib
in the location where it lives?
Boost.Build does inject a variety of paths into the system-specific pa
Hi,
I spent most of yesterday trying to get the simple tutorials and example to
build from within the Boost example folders, and finally succeeded. It was not
super straightforward as the instructions seem incomplete and out of date. But
after finding a tutorial on Boost.Build and understanding
What did you expect ? It's obvious that a given release of Boost.Python can not
make any compatibility guarantees about future Python releases
. . .
What's your point, exactly ? What are you trying to do ?
You're right. All I'm trying to do is gather information that I can submit and
hopefully
