Boost logo

Boost-Build :

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-12-16 02:55:46


jtorjo wrote:

>
>
> David Abrahams wrote:
>>
>>
>> There are no "settings" for directories that don't contain a Jamfile.
>> That said, however, it would be trivial to modify Boost.Build to allow
>> it. But is it an important use case? If it were, we'd surely have
>
> I would say it is, but this is just IMO. We'll have to wait and see...
>
> Again, in my case, this is very useful when building a library, and
> building examples and tests that all share some common settings.

Going back to your directory structure:

- examples [1]
šššš-šdialogs
šššššš-šexample1š[2]
šššššš-šexample2š[3]
ššššššš-š...
šššš-šcontrols
ššššššš-šcontrol_example1š[4]
ššššššš-šcontrol_example2š[5]
ššššššš-š...
šššš-š...
- win32gui
šššš-šsources
šššš-š...

you can just place a Jamfile in [1] what would define common setting. That
Jamfile need not define any targets to build, it will just define targets.
I still don't think it's much better if you can specify setting without
creating a file. After all, if somebody else has to built the project, he
has to use the same settings and file is a very convenient way to store
settings.

>> received a request for it by now (?)
>>
>
> I would say that bjam is very boost-oriented,

Boost.Build V2 is not so boost-oriented. In fact, it's now mostly used for
non-Boost projects, AFAICT.

> and from my experience,
> using it to build something else (in my case, win32gui), has proved
> quite painful.

Can you give some details so that we can improve?

- Volodya

 


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