Re: [Boost-build] Target paths idea

From: Jurko Gospodnetić (jurko.gospodnetic_at_[hidden])
Date: 2007-12-02 09:46:11

   Hi all.

> I had just got a totally crazy idea -- we have some algorithms
> to compute target paths, and --abbreviate-paths options, and it
> not quite good yet.

   I have another suggestion... (written directly as I am thinking of it 
in my head so do not scream too loudly if it does not make sense... :-) )...

   Allow a project to specify that some existing feature is always 'xxx' 
and should not be represented using a feature specific folder no matter 
how the feature itself is defined.

   That would mean that if a project needs to be built using different 
values for a single feature then that feature should get its own 
specific build folder, but if it does not then it should not.

   As a note - this would require that the build system prevent such 
project level settings from being violated.

   Another idea is to make it easy to create project specific 'group' 
features which would group together different feature values which would 
then cause only a single folder to be created for all those values. 
Hmmm... thinking of this now, I guess this can already be done using 
regular composite features (e.g. variant itself)... As in the previous 
suggestion the build system should make sure values specified for such 
related features are not in conflict with each other.

   Hope this helps...

   Best regards,
     Jurko Gospodnetić