[Boost-build] [V2] Problems with custom properties

From: Juergen Hunold (hunold_at_[hidden])
Date: 2006-02-26 08:15:50

Hi !

I've got some trouble with custom features.
I'm going to extend my Qt4-Toolset to build Qt4 with and without the 
Qt3Support module. I created a feature named "qt3support" with values 
"off on" and tried to control <define> and library creation by adding 
appropriate requirements and conditional <defines> based on the values 
of Qt3Support.
I've succeeded in creating two minimal testcase for the problems I 
encountered. I've replaced the original "qt3support" with "customized" 
to avoid confusion :-))

Please find to testcases against latest anon-CVS attached...

custon-feature-path:
When running "bjam --v2" in the project root, I get 

bjam Version 2
/home/hunold/packages/boost/tools/build/v2/build/feature.jam:430: in 
validate-value-string from module feature
error: "app/on" is not a known value of feature <customized>
error: legal values: "off" "on"

(full backtrace in error.txt in project root).
This bug is triggered by the "build-project app ; " line. I think this 
on is a bug because the path should never be added to the feature 
value.

custom-feature-property
Go to the "app" directory and run bjam --v2.

/home/hunold/packages/boost/tools/build/v2/build/targets.jam:756: in 
generate-really from module object(main-target)@143
error: failed to build ../a with properties <asynch-exceptions>off 
<customized>on <debug-symbols>on <exception-handling>on
 <extern-c-nothrow>off <inlining>off <link>shared <optimization>off 
<os>LINUX <profiling>off <rtti>on <runtime-debugging>o
n <runtime-link>shared <stdlib>native <threading>single 
<toolset-gcc:version>4.0 <toolset>gcc <variant>debug <warnings-as-
errors>off <warnings>all because no best-matching alternative could be 
found

(full backtrace again in error.txt at project root)
I believe this is a bug. Both "app" and "lib" have "<customized>on" in 
their requirements. 

I've alos tried several combinations of putting "<customized>on" in 
a) requirements
b) default-build
c) usage-requirements
with no real progress. All I got was the misterious bug from the first 
example...

So I'm stuck at this point in spacetime.

Yours,

Jürgen

-- 
* Dipl.-Math. Jürgen Hunold  ! Ingenieurgesellschaft für 
* voice: ++49 511 262926 57  ! Verkehrs- und Eisenbahnwesen mbH  
* fax  : ++49 511 262926 99  ! Lister Straße 15
* hunold_at_[hidden]          ! www.ive-mbh.de