Re: [jamboost] Re: v2: gcc and static linking

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-09-23 06:26:37

Hi Andre,

> > I should note that we can only generate command line line this
> >
> > <static libraries generated by boost.build>
> > -Wl,-Bstatic -lstatic_library_1, -Wl,-Bstatic_library2
> >
> > I.e. searched libraries will be always after those created by
> > Boost.Build. I guess that's OK?
> >
> > Anyway, I believe that in your case library order is not an issue? If so,
> > I'd recomment using linkflags for a while, until more users come
> > complaining.
>
> Here's a summary:
> - Library order is important so <linkflags> doesn't work. I tried.

The specific problem is that <linkflags> are added to the beginning of the 
command line, so references from the libraries/objects present later are not 
resolved, right?

> - searched libraries won't work. At least, I couldn't find a way
> to specify a full pathname for them, instead of using -l

Ah, you wanted to explicitly specify full path to the file? Yea, you're 
supposed to use "alias" for that -- which does not care about library order. 
The library order turns out to be *hard*!

> > If they come, the right thing to do, IMO, would be
> > 1. Drop <find-shared-library> and <find-static-library>, as they are not
> > symmetric and platfrom-specific.
> > 2. Add a new '<force-static-link>' feature. The name more accurately
> > reflects the behaviour of -Wl,-Bstatic
>
> That's a good idea. But then again, <force-static-link> would also be
> platform-specific.

Yes, but at least it's less confusing than the current features.

- Volodya