Re: fop rule broken?

From: Eric Niebler (eric_at_[hidden])
Date: 2004-12-30 13:48:47

David Abrahams wrote:
> David Abrahams wrote:
> 
>>And it doesn't even work for this weird cygwin/windows hybrid situation,
>>because guess what? The absolute paths created end up being cygwin
>>native paths. And I promise you, the code to detect that a windows
>>FOP/Java is being used and create absolute windows paths is even more
>>hackish.
> 
> 
> Okay, I checked in the horrible hacks that make this work. My
> user-config.jam now contains
> 
> using fop : c:/tools/fop-0.20.4/fop.bat
> : c:/WINDOWS/system32/java
> ;
> 
> Enjoy it in all the poor health it has brought to the codebase ;-)
> 

You're the Boost.Build expert, but not only does this *seem* wrong to 
me, it just doesn't work. When running under cygwin, you should be using 
fop.sh, not fop.bat. Besides, with fop-0.20.5, fop.bat *can* be invoked 
from a directory different from FOP_DIR.

To get this working on my machine, I had to revert your changes and 
reapply the change to common.variable-setting-command. It seems like the 
right fix. With this change, it works regardless of whether I run under 
cygwin or not.

I certainly wish Volodya would weigh in, though. Volodya, is there a 
reason why common.variable-setting-command does not currently export the 
new envar value?

-- 
Eric Niebler
Boost Consulting
www.boost-consulting.com