Thanks Eric. The tutorial was great. > According to Dan Smithers on 1/5/2009 5:01 AM: >> My goal is to be able to set up parallel debug and release builds for >> the different architectures. > > Yes, that is provided by VPATH builds, provided by Automake. > >> I would like to be able to build and link >> without having to "install" until I'm happy with the work. > > Yes, that is possible with DESTDIR support, also provided by using Automake. > >> I would also like to be able to build the complete project from the top >> level and also build sub-projects individually. > > Yes, that is provided by Autoconf. I set up parallel build directories and ran configure with extra arguments. build/gcc/debug ../../../configure CC=gcc CPPFLAGS=-DDEBUG CFLAGS="-O0 -g" build/gcc/release ../../../configure CC=gcc CPPFLAGS= CFLAGS="-O2" build/icc/debug ../../../configure CC=icc CPPFLAGS=-DDEBUG CFLAGS="-O0 -g" build/icc/release ../../../configure CC=icc CPPFLAGS= CFLAGS="-O2" The sub projects seem to compile correctly, but the linker needs to know which build it is using. Before I added the parallel builds I was building in the build directory. I could add paths like this: foo_LDADD="-lm -L$(srcdir)/../lib -l3rd_party_lib -L$(srcdir)/../../sublib/build/src -lsublib I want to be able to automatically replace build with build/gcc/debug etc. Is this something that autoconf can do? Is there a better way of achieving this? thanks dan _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf