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
On 03/20/2010 08:12 AM, Tim Post wrote:
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.
Traditionally, there are 2 primary reasons:
1) Multiple builds, e.g. building with
directory). But the makefile.ins
which generated by automake can no longer call subdirectory ones.
What should I do to implement this directory structure?
Thanks!
scleung
--
View this message in context:
http://old.nabble.com/Configure-script-not-at-the-root-of-src-directory-tp27947668p27947668.html
On 03/18/2010 10:06 AM, scleung wrote:
Now I want to put the scripts including configure to another directory
(i.e. in one of subdirectories of source directory).
Why? No one else does it that way. Configure is _always_ a top-level
file, per GNU Coding Standards. You aren't going to get
