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
According to
http://www.gnu.org/software/hello/manual/autoconf/Initializing-configure.html
I can do a AC_INIT(hello,1.0,[t...@test.com],[tarname],[http://www.test.com])
and expect to have PACKAGE* veritable set accordingly, see Makefile below.
But I can't see PACKAGE_URL got defined ?
I am
TJ,
On 3/20/2010 7:56 PM, TJ Yang wrote:
According to
http://www.gnu.org/software/hello/manual/autoconf/Initializing-configure.html
I can do a AC_INIT(hello,1.0,[t...@test.com],[tarname],[http://www.test.com])
and expect to have PACKAGE* veritable set accordingly, see Makefile below.
But I
Hi,
I ran autoscan and it gives:
configure.ac: warning: missing AC_PROG_RANLIB wanted by: ltmain.sh:1601
So i added AC_PROG_RANLIB and ran autoreconf and now it says:
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal -I m4
