Re: [jamboost] bbv2-m10: how to differ .obj build dir by using <define> (similar to debug vs release)?

From: Andrey Melnikov (melnikov_at_[hidden])
Date: 2005-08-01 14:23:10

Vladimir Prus wrote:
> Hi,
> 
> 
>>When building release vs debug, the .obj directories are automatically
>>different so I don't have to do a clean build when switching between
>>them. This works great so I'm wondering if a similar feature exists to
>>work with a specific <define>.
>>
>>Basically, I'm trying to avoid having to do a clean build when switching
>>between 'standard' and 'professional' builds of the project which is
>>controlled by a <define>.
>>
>>I'd like these preprocessor-controlled 'standard' and 'professional'
>>builds to use a separate dir for .obj files during the build.
>>
>>Any suggestions or workarounds would be deeply appreciated.
> 
> 
> There's no way to represent "define" in build path, however you can created 
> your own new features and make it expand to desired defines. Like this:
> 
> import feature ;
> feature.feature djb-build-kind : standard professional : propagated
> composite ;
> feature.compose <djb-build-kind>standard : <define>STANDARD_BUILD ;
> feature.compose <djb-build-kind>professional :
> <define>PROFESSIAONAL_BUILD ;
> 
I think "standard" is a build variant, not a feature. The proposed 
scenario is good only if DJB wants to build all 4 variants (debug-std, 
debug-pro, release-std, release-pro)

Andrey