On 31-3-2011 2:56, Steve M. Robbins wrote:
My understanding of the use-case is: suppose you are using Boost.Build to build a project that contains a library as well as an executable linked with that lib. If the library is built as a shared object, the hardcode-dll-paths lets you build and run the executable in-place.
I assume you mean you can run the exe without having to install the libs to known paths?
Olaf -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
