Hi all,
Sorry if this is already in the archive. I looked through it and was
not lucky. You must also know that I am quite new to autoconf but... I
need to learn fast!
I want to implement the --with-package=DIR option to my project's
configure script. The --with-package[=yes|no] thing
Hi.
Im currently trying to trans fare a large amount of projects form ad-hoc
Makefiles to automake and autoconf. One of the objectives for this
trans fare is it get debian packages for "free". Meaning that when the
build is ok the dpkg-buildpackage does the job of making packages.
To make a
Hello all,
I'm a beginner new on this list searching for enlightnment on the usage
of Autoconf (and friends).
I've just arrived to a new project were we have to maintain (debug,
upgrade, new features, etc) a certain amount of software which must be
executed (mostlly dynamic loaded libraries .so)
Aslak Johannessen wrote:
> Im currently trying to trans fare a large amount of projects form ad-hoc
> Makefiles to automake and autoconf. One of the objectives for this
> trans fare is it get debian packages for "free". Meaning that when the
> build is ok the dpkg-buildpackage does the job of m
On Jul 5, 2007, at 1:29 PM, Thomas Lavergne wrote:
Hi all,
Hello Thomas,
Sorry if this is already in the archive. I looked through it and
was not lucky. You must also know that I am quite new to autoconf
but... I need to learn fast!
I want to implement the --with-package=DIR opt
On Thu, Jul 05, 2007 at 02:59:19PM +0200, Aslak Johannessen wrote:
> Much of this information is duplicated and the "need" for a
> centralized configuration file for each project is wished for.
Ideally, you pass everything to configure and get everything done by
make install, so nothing is duplica
Aslak Johannessen wrote:
To make autoconf automake and dpkg-buildpackage run one needs to edit
and type information into many different files. Mainly Makefile.am
configure.in and debian/control. Much of this information is duplicated
and the "need" for a centralized configuration file for each
I want to implement the --with-package=DIR option to my project's
configure script. The --with-package[=yes|no] thing is straightforward
using AC_ARG_WITH(). I have however some questions regarding others'
experience wth the =DIR part.
1. What should I do if the user is so dumb to actually