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 at least I’ve got it to work. * Andy From: Cplusplus-sig <cplusplus-sig-bounces+jandyman.voelkel=gmail....@python.org> on behalf of stefan <ste...@seefeld.name> Reply-To: Development of Python/C++ integration <cplusplus-sig@python.org> Date: Wednesday, May 22, 2019 at 11:36 AM To: "cplusplus-sig@python.org" <cplusplus-sig@python.org> Subject: Re: [C++-sig] Getting simple boost.python extension to work outside the test scripts - HELP! 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 library dependencies. [Stefan] -- ...ich hab' noch einen Koffer in Berlin...
_______________________________________________ Cplusplus-sig mailing list Cplusplus-sig@python.org https://mail.python.org/mailman/listinfo/cplusplus-sig
