Re: [Boost-build] conditional rules: arguments

Subject: Re: [Boost-build] conditional rules: arguments
From: Gaydov Victor (victor.gaydov_at_[hidden])
Date: 2009-09-14 10:29:57

> Victor,
> 
> the "general" reason is that free features tend to be used for 'raw' things
> that are passed to the underlying thing, and therefore are not considered in
> many contexts.
> 
> I don't know if in this case, specifically, passing free features to conditional
> functions will break anything or not. Can you let me know your actual use case,
> so that I can properly consider this behaviour?

well, i was writing helper rules to work with config file. config (just
a jamfile) is specific for target-os -- i'm cross-compiling -- and
provides include and library paths, names, versions, etc. for example,
this:

 searched-lib loki
        :
        : <conditional>@config.library <config:library>LOKI
        ;

will search config depending on target-os, then search in config
LOKI_INC, LOKI_LIB, etc and add properties to 'loki' target.

so, <config:library> should be passed to @config.library. is it right
that i can't have multiply values of non-free features ? as i
understand, yes, and i need; so <config:library> is free.

making it incidental solved the problem and it is passed to the rule.

--
Gaydov Victor.
I knew I'd hate COBOL the moment I saw they'd used "perform" instead of
"do".
		-- Larry Wall on a not-so-popular programming language