From: JÃ¼rgen Hunold (hunold_at_[hidden])
Date: 2004-11-11 10:04:51
Hi Volodya !
On Thursday 11 November 2004 15:31, Vladimir Prus wrote:
> Hi JÃ¼rgen,
> > So, I'm not sure how to resolve this.
> > The only thing I know for sure is that the custom link options in
> > toolset initialisation should be inserted _before_ all other option
> > in order to override them.
> Actually the reason the options are added to the end is that if you
> use something like <linkflags>-lsome_static_lib, things won't link if
> -lsome_static_lib is added to front of command line, and some
> libraries later on the command line use symbols from some_static_lib.
Well, I've had to hack gcc.jam to use -Wl,"-(" and -Wl,"-)" in order
to navigate around cyclic dependencies in my *lots* of legacy code :-((
So this does not matter to me, but people with a better library design
will of course care ;-))
Yes, I see the design decision.
But this won't work for sun.jam, because this has OPTIONS on the front
of the link action (or the sun linker does some strange things, I don't
> Unless somebody has bright ideas, I think the only solution is to
> have OPTIONS_BEFORE and OPTIONS_AFTER variables, and convert
> <linkflags> to OPTIONS_BEFORE, which will be added to the front of
> command line.
This would at least solve my problem but introduce problems with the
scenario noted above. *sigh*
-- * Dipl.-Math. JÃ¼rgen Hunold ! Institut fÃ¼r Verkehrswesen, Eisenbahnbau * voice: ++49 511 762-2529 ! und -betrieb, UniversitÃ¤t Hannover * fax : ++49 511 762-3001 ! Appelstrasse 9a, D-30167 Hannover * hunold_at_[hidden] ! www.ive.uni-hannover.de
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