Re: [C++-sig] Getting simple boost.python extension to work outside the test scripts - HELP!
stefan via Boost-build <[email protected]> Wed, 22 May 2019 14:33:15 -0400
| Newsgroups | gmane.comp.lib.boost.build,gmane.comp.python.c++ |
|---|---|
| Message-ID | <[email protected]> |
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...
_______________________________________________
Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build