On Apr 11, 2005, at 7:31 AM, Axel Weiß wrote:
James, did you already develop a strategy for eliminating runConfigure?
Hi Axel,
Sorry the for the delay in replying, I've been out of town for a day.
Yes. I've got prototype autoconf infrastructure that eliminates both runConfigure and the need for XERCESROOT (as least as far as the build and test infrastructure is concerned). The options for runConfigure are sniffed into reasonable defaults by default; they can be overridden by --with and --without. So I think your comments are completely inline.
This code is due to be checked into just as soon as we switch to svn and can start a broader reorganization of things. That seems to be held up by apache infrastructure at the moment, but hopefully we'll break it free soon.
The other major task in supporting the broad variety of platforms is to refactor the Platform support, as well as write additional autoconfig test for various bits of functionality.
See an earlier status email I sent on this subject (Feb 24), another email I sent regarding some autoconf thoughts (Feb 17), and our general release 3.x plan (releases_plan.html document in cvs -- I guess it never made it to the site).
Your thoughts, comments and help are all welcome. Hopefully we'll get the svn stuff out of the way relatively soon so we can more readily begin our 3.x migration.
James.
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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
