Jason van Zyl wrote:
>
> I think all you should need is a gump.properties file for your machine
setup
> and a profile for what you want to build. I don't think there's a need
for a
> workspace descriptor at all.
I'd like to do more than simply define configuration parameters - I'd like
to be able to tailor the workspace and even add definitions.
If you really find XML syntax that distasteful and can live with a subset
of function, perhaps a small program could be written which reads in a
properties file and builds a workspace file for you?
> I have been trying to use Gump to build the TDK for close to six months
> now,I can get it to work. It's the configuration that's a PITA because
the
> workspace was bound to your machine. If you remember I sent a (somewhat
> crude) set of patches that allowed a set of properties to be fed into the
> workspace so that it would make it easier for me to build the TDK. It
worked
> but you wanted to use an XML description and the patches were never
applied.
The workspace definition has gotten pretty simple (IMHO). What inhibiting
PITAs are left?
- Sam Ruby
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
