Subject: Re: [Boost-build] shared library naming on windows
From: Bo Jensen (jensen.bo_at_[hidden])
Date: 2010-08-10 09:57:34
On Tue, Aug 10, 2010 at 3:43 PM, Bo Jensen <jensen.bo_at_[hidden]> wrote:
> On Tue, Aug 10, 2010 at 3:01 PM, Vladimir Prus <ghost_at_[hidden]> wrote:
>> On Tuesday 10 August 2010 14:27:38 Bo Jensen wrote:
>>> I am building a shared library on windows, which is build correctly
>>> with .dll extension, but when linking into a exe application the
>>> linker looks for .lib extension and fails.
>> Could you provide the exact error message?
> It is the same with or without the no auto linking option :
> LINK : fatal error LNK1104: cannot open file 'bin\intel-win\debug\threading-mult
> call "C:\Programmer\Intel\Compiler\11.1\065\bin\ia32\iclvars_ia32.bat" >
> xilink /DEBUG /subsystem:console /out:"bin\intel-win\debug\threading-multi\sulum
> .exe" @"bin\intel-win\debug\threading-multi\sulum.exe.rsp"
> if %ERRORLEVEL% NEQ 0 EXIT %ERRORLEVEL%
> ...failed intel-win.link bin\intel-win\debug\threading-multi\sulum.exe bin\intel
> ...failed updating 2 targets...
> ...updated 92 targets...
> But in the build process it clearly builds a sulum-lib.dll i.e not
>>> The library is included
>>> into the exe build as :
>>> and no other link options is used on command line. The library
>>> "somelib" is including several boost libraries which is linked
> In my project specs I got :
> which are the libraries used in the code for the sulum-lib.dll, I want
> to link them static.
> Is -d2 the right command to get debug information at linking ?
>> Could you clarify what is "linked statically"?
>>> can this be the problem ?
>>> I am using intel for compile and linking with msvc8.
>>> Any help is appreciated.
>> You might want to have <define>BOOST_ALL_NO_LIB to disable autolinking.
I added this into my Jam file, but I don't see it when I run with -d2,
should I ?
>> Vladimir Prus
>> Boost.Build: http://boost.org/boost-build2
>> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk