Hi Gareth, hi James,
Gareth Reakes wrote:
> Hi Axel,
>
> Axel Weiß wrote:
> > you mean, you want to get rid of the awkward runConfigure script?
> > :)
>
> Oh yes :)
>
> > Sure, I'd like to help. It doesn't seem to be too complicated,
> > either. Who is currently working on this? Is there any strategy in
> > mind?
>
> James is sorting this out. I am sure he would love your help :)
James, did you already develop a strategy for eliminating runConfigure?
A brief analysis shows to me two main tasks of runConfigure:
1. offer to the user a convenient way to specify platform, compiler and
xerces-modules like transcoder, net accessor and message loader
2. set some environment variables according to the user's choice (which
are then used by configure only).
So one possible way to eliminate runConfigure could be:
1. map the arguments of runConfigure to arguments of configure. There
are some standard-ways to pass configure-arguments (e.g. platform would
be --target, misc-options would be --with-* or --without-*), and
configure tends to determine the compiler by it's own, if the CC
environment variable is not set.
2. Integrate the functionality of runConfigure into configure.in. All
the environment variables exported by runConfigure can then be dropped.
3. configure and configure.in should be moved to $XERCESCROOT. This
would require to have also a Makefile.in in $XERCESCROOT.
4. The environment variable XERCESCROOT may be eliminated as well.
Any comments on this?
Axel
--
Humboldt-Universität zu Berlin
Institut für Informatik
Signalverarbeitung und Mustererkennung
Dipl.-Inf. Axel Weiß
Rudower Chaussee 25
12489 Berlin-Adlershof
+49-30-2093-3050
** www.freesp.de **
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
