Re: [Boost-build] recursively call unit test executable

Subject: Re: [Boost-build] recursively call unit test executable
From: Tim Blechmann (tim_at_[hidden])
Date: 2018-11-04 18:31:46

>> `std::system()` isn't able to resolve the dynamic libraries, so it fails
>> with:
>>> dyld: Library not loaded: libboost_chrono.dylib
>>>   Referenced from: /Users/tim/dev/boost/libs/lockfree/test/../../../bin.v2/libs/lockfree/test/queue_interprocess_test.test/darwin-4.2.1/debug/threadapi-pthread/threading-multi/visibility-hidden/queue_interprocess_test
>>>   Reason: image not found
[snip]
> The executable runs because DYLD_LIBRARY_PATH is set.
> Is this somehow not being inherited or is system() not
> respecting it?
> 
> Possible workarounds:
> - <hardcode-dll-paths>on or,
> - <link>static

actually i was using `hardcode-dll-paths`, but didn't have an effect ...
`static` linking works, will go that route ... thanks a lot!