Boost logo

Boost-Build :

From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-08-06 04:02:54

Markus Schöpflin wrote:
> Vladimir Prus wrote:
> > Can you clarify: do you need some linker option to appear precisely at
> > the end of linker command line (i.e. the order matters), or you're trying
> > to change the command line according to output from some other program?
> I will try, I hope it's more clearly this time. (Sometimes I wish
> I had a better skill with english than with comptures... :-)
> I have a ton (30 to 40 lines!) of -L and -l options (generated by
> an external makefile) which must appear at the end of the linker
> command line exactly as generated by the makefile in order to link
> the application correctly.

OK. Guess I should go into some details. In order to perform any build
action, the build system loads appropriate toolset file (is it msvc in your
case?). It then uses "flags" rule to create a variables based on required
properties, which variables are used in build actions.

Precisely, you have <linkflags>x
msvs-tools.jam has
flags LINKFLAGS <linkflags> ;
which cause all values of <linkflags> properties to be added the the variable
LINKFLAGS. Then, rule called
vc-Link uses that variable.

Now, how is it all related to your question. I think that order ot options
will be retained in any case. If you look at vc-Link rule you'll notice that
it uses LINKFLAGS not in the end of command line. Don't know why, actually --
I actually have no idea about options order even for gcc :-)

You can try moving LINKFLAGS to the end of command line in vc-Link and see if
this works. Otherwise,
a new variable would have to be introduced, similar to LINKFLAGS.

- Volodya


Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at