Building libraries with no mangling
Hi, I've been doing a lot of Googling on this issue and I haven't found a resolution. How can I prevent the boost build process from mangling the library names? I invoke bjam as follows: bjam --toolset=msvc debug stage I would like normal names for the libraries, like: boost_signals.lib and boost_signals.dll. Thanks.
On 19/02/2008, Robert Dailey <rcdailey@gmail.com> wrote:
Hi,
I've been doing a lot of Googling on this issue and I haven't found a resolution. How can I prevent the boost build process from mangling the library names?
I believe you can do this by adding "--layout=system" to your command line. Hope that helps, Darren
On Feb 19, 2008 4:56 PM, Darren Garvey <darren.garvey@gmail.com> wrote:
I believe you can do this by adding "--layout=system" to your command line.
Hope that helps, Darren
Yes, this does help. Thank you. One other thing I'm trying to figure out is how to force bjam to only build the multithreaded debug DLL version of boost. Even by doing the --help command I didn't see any way of doing this. Help on this issue would be appreciated too.
Hi Robert.
One other thing I'm trying to figure out is how to force bjam to only build the multithreaded debug DLL version of boost. Even by doing the --help command I didn't see any way of doing this. Help on this issue would be appreciated too.
How about adding 'debug' (or 'variant=debug'), 'threading=multi' and 'link=shared' to the command line (quotes not included)? Best regards, Jurko Gospodnetić
Robert Dailey wrote:
How about adding 'debug' (or 'variant=debug'), 'threading=multi' and
'link=shared' to the command line (quotes not included)?
I tried that too and it still generated "link-static" folders.
All of them? Or some specific link-static folders? If there latter, and those folders belong to a library, then which one? Maybe that library wants to be built as static one. - Volodya
participants (4)
-
Darren Garvey -
Jurko Gospodnetić -
Robert Dailey -
Vladimir Prus