Hmmm ... I'm not sure I understand ...
My 'configure' script is in 'topdir' (or preferably in 'topdir/config' but
that's a different story). 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.
A later invocation of configure on 'arch2' would then create the
corresponding arch2 directories.
All this sort of works with the hack in AC_OUTPUT, but VPATH gets eaten as
described in my first mail.
Rasmus
On Wed, 28 Feb 2001, Derek R. Price wrote:
> No, really. In the scenario you describe, your build tree has simply become a
> subdir of the source tree. Using your example, assuming that your configure
> scripts are in topdir/src/package?, and ignoring the fact that cd probably isn't
> going to open me a shell on another platform:
>
>
> cd topdir/src/package1
> mkdir arch1 arch2
> cd arch1
> .../configure
> make all check install
> cd ../arch2
> ../configure
> make all check install
> ...
>
> cd ../../topdir/src/package2
> mkdir arch1 arch2
> cd arch1
> .../configure
> make all check install
> cd ../arch2
> ../configure
> make all check install
> ...
>
> . . .
>
> Derek
>
> --
> Derek Price CVS Solutions Architect ( http://CVSHome.org )
> mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
> --
> I've never made a mistake in my life. I thought I had once, but it turned
> out that I hadn't.
>
> Rasmus Tamstorf wrote:
>
> > On Wed, 28 Feb 2001, Derek R. Price wrote:
> >
> > > Rasmus Tamstorf wrote:
> > >
> > > > AC_OUTPUT([src/_$ARCH/Makefile:src/Makefile.in])
> > >
> > > You know, there's a much more painless way to do this. Autoconf already knows
> > > that if you:
> > >
> > > mkdir $ARCH
> > > cd $ARCH
> > > ../configure
> > >
> > > Then the build tree will be created automatically in and under the current
> > > directory. That's the whole point of the $srcdir variable in the first place.
> > > In this scenario, srcdir will be set to ../XXX where XXX is each subdir
> > > configure is creating a Makefile (or other file) in.
> >
> > I know that much (but thanks anyway :) The point is that my source code is
> > made up of multiple packages, and I'd like the build objects to live close
> > to the source code rather than in a separate build tree. I.e. something
> > like :
> >
> > topdir/
> > src/
> > package1/
> > arch1/
> > arch2/
> > ...
> > package2/
> > arch1/
> > arch2/
> > ...
> >
> > instead of
> >
> > topdir/
> > arch1/
> > src/
> > package1/
> > package2/
> > arch2/
> > src/
> > package1/
> > package2/
> >
> > I know that the latter is what the gnu tools use, but people here like it
> > the other way, so I'm trying to make that work.
> >
> > Rasmus
> >
> > -----------------------------------------------------------------------------
> > [EMAIL PROTECTED] "A problem worthy of attack,
> > Walt Disney Feature Animation proves its worth by hitting back" Kumbel
> > -----------------------------------------------------------------------------
>
>
-----------------------------------------------------------------------------
[EMAIL PROTECTED] "A problem worthy of attack,
Walt Disney Feature Animation proves its worth by hitting back" Kumbel
-----------------------------------------------------------------------------
