Re: fop rule broken?

From: David Abrahams (dave_at_[hidden])
Date: 2004-12-29 22:13:10

Eric Niebler wrote:

> 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?

It's not the right fix; it breaks HTML generation. The problem is that
on Unix systems, the

<VARIABLE>=<value> <command>

(all on the same line) syntax is used.

Anyway, I'm not seeing the same problem as you are. For me, it's:

cd c:/boost/tools/build/v2/doc/src/
cd .. && bash -c "bjam --v2 pdf"
/cygdrive/c/boost/tools/build/v2/tools/boostbook.jam:335: in
object(boostbook-generator)@1.run from module object(boostbook-generator)@1

And having changed that to

I'm not sure about you, but I appear to be working with a cygwin bjam
invoking a Windows install of Java and fop. Here's what I did to get it
to work:

copy the fop.bat file to my personal bin directory, c:/bin.
Adjust all the relative paths in c:/bin/fop.bat so they point to the
same directory they would have if interpreted relative to the original
fop.bat's directory.

Now:

using fop : /cygdrive/c/bin/fop.bat
: c:/WINDOWS/system32/java
;

Njoy,
-- 
Dave Abrahams
Boost Consulting
http://www.boost-consulting.com