[C++-sig] Getting simple boost.python extension to work outside the test scripts - HELP!

[stefan]

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 theory this 
> wouldn’t a problem, because I wouldn’t need to set DYLD_LIBRARY_PATH.
>
> Is this insertion of the path of libboost_python37.dylib into 
> hello_ext.so something I can do with bjam, or am I going to have to 
> figure out how to use a separate build system?
>
I'm cross-posting this to the Boost.Build mailing list, since that's the 
best (only ?) place where you'll get an answer to this question.


Stefan

--

       ...ich hab' noch einen Koffer in Berlin...
     

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cplusplus-sig/attachments/20190522/df7b659a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.png
Type: image/png
Size: 1478 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/cplusplus-sig/attachments/20190522/df7b659a/attachment-0001.png>