Re: [jamboost] The FOP tool (Was: [Boost-build] CVS: boost/tools/build/v2/tools fop.jam,1.1,1.2)

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-11-03 03:25:02

On Monday 01 November 2004 15:08, Aleksey Gurtovoy wrote:

> > rule fop-to-print
> > {
> > ........
> > PATH_SETUP on $(target) =
> > [ common.variable-setting-command JAVA_HOME : $(JAVA_HOME) ]
> > }
> >
> > actions fop
> > {
> > $(PATH_SETUP)
> > ......
> > }
>
> Feel free to adjust this as you deem appropriate. FWIW, you still have to
> invoke either 'fop.bat' or 'fop.sh' depending on the platform.
>
> > Another issue is that fop.jam requires user to specify path to FOP, while
> > all the compilers require full path to executable. If we used the same
> > syntax for fop, there would be no reason to decide if "fop.bat" or
> > "fop.sh" should be used.
>
> Right.

Adjusted by using command name as parameter and 
common.variable-setting-command...

> > Doug, what would you say if I change fop.jam to accept the fop *command*,
> > not path? There's no need to push this into this release, though.
>
> Yes, not on the branch please.

... on trunk.

- Volodya