Subject: [Boost-build] somelib/link<static> doesn't work
From: Steve Jaffe (sjaffe_at_[hidden])
Date: 2010-07-15 15:15:17
According to the docs, it seems this should link to the static library
'mylib', but it doesn't (and since there's no shared version, the link step
exe myexe : somefile.cpp /myproj//mylib/<link>static ;
But more strangely, if I specify the library directly rather than using the
project// notation, then it tries to make every library involved in the
linking to be static! i.e.
exe myexe : somefile.cpp mylib/<link>static
Am I doing something wrong?
(This is the relevant doc:
We can also use the <link> property to express linking requirements on a
per-target basis. For example, if a particular executable can be correctly
built only with the static version of a library, we can qualify the
executable's target reference to the library as follows:
exe important : main.cpp helpers/<link>static ;
No matter what arguments are specified on the bjam command line, important
will only be linked with the static version of helpers.
-- View this message in context: http://old.nabble.com/somelib-link%3Cstatic%3E-doesn%27t-work-tp29176743p29176743.html Sent from the Boost - Build mailing list archive at Nabble.com.
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