On Thu, 2010-03-18 at 09:25 -0700, scleung wrote: > Hi, > > Usually we use autoscan to scan the source directory structure to > generate configure.ac file and finally generate configure script in the root > of source directory. > Now I want to put the scripts including configure to another directory > (i.e. in one of subdirectories of source directory). But the makefile.ins > which generated by automake can no longer call subdirectory ones. > What should I do to implement this directory structure? > for example: > the structure is like this: > build\ -- configure scripts located in this directory > src\ -- source files > test\ -- test files A better method would be to allow the user to do that. For instance: foo@bar# ls . .. src/ test/ foo@bar# mkdir build foo@bar# cd build foo@bar# ../configure foo@bar# make ... etc ... With very few exceptions, however, I don't see the use of _not_ dirtying up the source directories with objects and other output if proper cleaning targets exist. Cheers, --Tim _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
