From: Jurko GospodnetiÄ (jurko.gospodnetic_at_[hidden])
Date: 2008-08-26 11:41:05
> Here is my problem, i try to link a shared library to unit-test target :
> unit-test testsys : [ glob *.cpp ]
> /plugone//plugone/<link>shared ;
> but if i have a look at the output ( -d2 ), i can see :
> file .......testsys.exe.rsp
> For me that means plugone.lib is linked statically to the testsys.exe but
> i'm not sure at all, i would like to know if this behavior is normal and if
> yes why?
Are you sure they are getting linked statically? The .lib files (i.e.
import libraries) would get created even when building shared libraries.
What were the exact options used when linking your testsys executable?
Does your testsys executable start successfully when the plugone.dll
is not present?
When you look at the build testsys executable using Microsoft's
Dependency walker (depends.exe) or some similar tool, do you see
plugone.dll listed as one of the shared libraries it depends on?
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