Rasmus Tamstorf wrote:
> Hmmm ... I'm not sure I understand ...
>
> My 'configure' script is in 'topdir' (or preferably in 'topdir/config' but
> that's a different story).
Autoconf always assumes it is in topdir. I suspect there's no easy way to work around
that.
> Furthermore I'd like to be able to run
> 'configure' just once per platform, and then have it create the
> appropriate subdirectories for each source directory. So I would do
> something like
>
> cd topdir
> ./configure
>
> and assuming that I'm on 'arch1' that would create
>
> topdir/
> src/
> package1/
> arch1/
> package2/
> arch1/
>
> along with the set of Makefiles specified in AC_OUTPUT.
Oh. Well,
topdir/
src/
package1/
package2/
arch1/
arch2/
Would be a lot easier. Then the magic is just
cd topdir/arch1
../configure
and the following structure will be created:
arch1/
src/
package1/
package2/
Maybe that's not exactly what you wanted, but Autoconf is already set up to handle it.
Note that all the source files not generated by configure will still be under topdir/,
not topdir/arch?, and a properly constructed Makefile will still be able to find them.
The idea is that the build area will mirror the structure of the source area, so
topdir/arch1/src/package1 should have files built from sources in
topdir/src/package1...
These aren't separate projects, are they? Such that they could each have their own
configure script and a controlling Makefile that would cause a build to descend into
each arch-specific directory, run the appropriate configure script, and then run each
build?
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
Mud is not one of the 4 food groups.
Mud is not one of the 4 food groups.
Mud is not one of the 4 food groups...
- Bart Simpson on chalkboard, _The Simpsons_
