Re: fop rule broken?

From: Eric Niebler (eric_at_[hidden])
Date: 2004-12-29 20:43:32

Eric Niebler wrote:
> 
> David Abrahams wrote:
> 
>> Title says it all.
>>
>> I can bjam --v2 html but not bjam --v2 pdf
>> How is it done?
>>
> 
> I think this is broken as well, at least under cygwin.

I spent some time today tracking this down. There are two problems. 
First is that in November, Volodya changed the fop rule to accept a 
FOP_COMMAND instead of a FOP_PATH, but the documentation doesn't reflect 
that change.

The second problem took some more hunting, and it turns out to be due to 
the common.variable-setting-command rule in common.jam. For *nix 
systems, the rule evaluates to:

return "$(variable)=$(value)" ;

This sets the environment variable but doesn't export it. In the case of 
the fop rule, the JAVA_HOME envar needs to be exported so that an 
invocation of the FOP_COMMAND can see it.

I recommend changing the common.variable-setting-command on *nix systems 
to evaluate to:

return "$(variable)=$(value);export $(variable)" ;

I don't really know bjam/Boost.Build, so I can't predict what sort of 
havok this change would wreak, but it does fix the problem with fop.

Comments?

-- 
Eric Niebler
Boost Consulting
www.boost-consulting.com
-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.298 / Virus Database: 265.6.6 - Release Date: 12/28/2004