|
From: Andreas L. <no...@sb...> - 2001-10-23 00:11:04
|
On Mon, 2001-10-22 at 23:44, Eric Bezault wrote:
> Andreas Leitner wrote:
> >
> > Ok, given that -D is the more correct way to go, I'll change gexace to
> > to use that instead of --define.
>
> But can't we support both syntax? That's what I already
> suggested for 'geant'.
Sure, thats also possible.
Btw, how can i pass options from geant to gexace currently?
I know I can nest <define> elements in <gexace> elements, but how can I
make them conditional?
The following works:
<gexace command="build" command_options="ise">
<define name="foo1" value="bar1"/>
<define name="foo2" value="bar2"/>
<define name="foo3" value="bar3"/>
</gexace>
but I need some way to only define a gexace variable if the geant
variable has also been defined:
<gexace command="build" command_options="ise">
<define name="foo1" value="${FOO1}" if="${FOO1}"/>
<define name="foo2" value="${FOO2}" if="${FOO2}"/>
<define name="foo3" value="${FOO3}" if="${FOO3}"/>
</gexace>
or some other way to archive a similar effect without needing to write
2^n tasks for n options.
tia,
Andreas
|