Re: [Boost-build] Install rule and default-build

Subject: Re: [Boost-build] Install rule and default-build
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2010-06-11 09:13:07

On 6/10/2010 4:30 PM, Anthony Foglia wrote:
> It seems that the install rule does not handle default build settings
> like other rules do. I currently have this install rule which works fine.
>
> explicit install ;
> install install
> : $(converters)
>
> : <variant>release:<location>Release/$(project-name)
> <variant>debug:<location>Debug/$(project-name)
> ;
>
> Where converters is a list of executables, and project names is a string.
>
> Now if I want to make this a default-build setting (so I can perhaps
> override it from a higher Jamfile) like so:
>
> explicit install ;
> install install
> : $(converters)
> :
> : <variant>release:<location>Release/$(project-name)
> <variant>debug:<location>Debug/$(project-name)
> ;
>
> I get the following error when running "bjam release install":
> error: legal values: "debug" "release" "profile" "debug-python"
> "production"
>
> Shouldn't moving a requirement to default-build not break anything as
> long as I don't try to override it?

Not the way you have it.. Specifically you can't have *conditional* 
requirements in the default build. You would need to change you example to:

explicit install ;
install install
   : $(converters)
   : <variant>release:<location>Release/$(project-name)
     <variant>debug:<location>Debug/$(project-name)
   : <variant>release
;

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org (msn) - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail