|
Boost-Build : |
From: Daniel Einspanjer (deinspanjer_at_[hidden])
Date: 2006-02-04 16:30:32
There are a few things that I don't like about the order in which the
feature subdirectories are created in build-dir.
I've created a new feature called customer, and I'd like that feature to
come first, before even debug or release so that the output files for
customers are logically grouped.
After that would be the variant subdir.
After that, I'd like to declare the default toolset for each platform and if
that toolset is used, I'd prefer not to see the toolset name in the
build-dir. It would be okay to see a non-default toolset however.
After that, I'd like no further features to be subdirs unless they are not
part of our standard feature defaults.
I have gone through the user manual and I don't see anything about changing
the order of the subdirs. I did post a thread about changing some of the
defaults for some features. I tried that, and it worked for eliminating some
of the extra subdirs, but not all of them (notably I still get a
runtime-debugging-off subdir).
Does this sound like a reasonable thing to wish to do? Can anyone give me
some tips or point me at any documentation that would help me to this end?
Thanks,
Daniel
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