Subject: Re: [boost] Boost build problem
From: Emil Dotchevski (emildotchevski_at_[hidden])
Date: 2009-09-24 02:02:29
Volodya, thanks -- it turned out I forgot the BOOST_ALL_NO_LIB.
I have another related question. If I don't use <runtime-link>static,
obviously the built executable needs the runtime DLLs. My question is,
is there a way to specify a directory dependent on the MSVC version
that contains the necessary runtime dlls so that Boost Build can run a
target that was successfully built?
(Arguably, what I'm asking for shouldn't be supported, since the
correct way to do this is to have multiple versions of Visual Studio
properly installed, whereas I only have VC9 installed, from VC8 I just
have the compiler/linker, libraries, runtime DLLs, etc. copied in a
Reverge Studios, Inc.
On Wed, Sep 23, 2009 at 10:36 PM, Vladimir Prus
> Emil Dotchevski wrote:
>> I'm trying to use <link>static and <runtime-link>static with my own
>> code, which depends on boost filesystem, and I have the problem that
>> the linker is passed libboost_filesystem-vc80-mt-sgd-1_41.lib while
>> the debug\link-static\runtime-link-static folder has
> in general, it's best to provide the exact command(s) you are running,
> and the exact error output from whatever tool emit error. If you
> have Boost.Build project that depends on Boost, I'd recommend setting
> <define>BOOST_ALL_NO_LIB in project requirements, as the autolink only
> works if all of Boost is built and installed into some directory, and
> that directory is added to library search path -- and none of this
> should be necessary as Boost.Build can directly link to right library
> without any autolink at all.
> - Volodya
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk