Boost logo

Boost-Build :

From: David Abrahams (dave_at_[hidden])
Date: 2003-10-20 03:50:03

Vladimir Prus <ghost_at_[hidden]> writes:

> David Abrahams wrote:
>> > I'd appreciate all comments on this document.
>> I got lost trying to read the table. I don't understand the meaning
>> of the row and column headings.
> I've added the following to the document:
> The header of the table contains three linking options for the "b" library.
> The "B creates" row explains which targets are generated by "b" when those
> linking options are used. Finally, three remaining rows list linking options
> for the "a" library and tell what "a" does with the targets produced by "b".
> Did this clarify anything?

Yes, thanks. Now, IIUC:

a. you are proposing to have both "bubble-up" and "automatic" linking
b. These are really the same thing when linking statically


Why allow both? You wrote:

"It was proposed by Ali, IIRC, that putting library in sources of
other library does the right thing: use direct linking if the
library is build as shared, and use bubble-up if library is linked
as static."

If that's the "right thing", allowing both seems overly complicated.
One simple syntax should achieve what you want. Probably I'm missing

Dave Abrahams
Boost Consulting

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