Le 23 sept. 08 à 23:08, Ralf Wildenhues a écrit :
Hi Akim,
Hi Ralf!
* Akim Demaille wrote on Tue, Sep 23, 2008 at 04:35:50PM CEST:
I'm slowly getting rid of my recursive Makefiles. Instead I have one
local.mk per directory, and a few Makefile.ams that include them. Of
course I have to
On Wednesday 24 September 2008 06:54:50 Ralf Wildenhues wrote:
* Bryan Bennetts wrote on Tue, Sep 23, 2008 at 05:01:21PM CEST:
If I do include the aclocal.m4, the configure *still* kicks off
automake because of a subdirs file that is created by configure being
newer than the
Ralf Wildenhues [EMAIL PROTECTED] writes:
* Akim Demaille wrote on Tue, Sep 23, 2008 at 04:35:50PM CEST:
I'm slowly getting rid of my recursive Makefiles. Instead I have one
local.mk per directory, and a few Makefile.ams that include them. Of
course I have to prefix all my file names
(I'm an autotools newbie.)
What is the automake sanctioned way of providing different top-level
make targets, that build my application with different options?
For example, say I want to build foo_nondebug, and foo_debug, and
(luckily) all of my application code resides in the
Peter,
On Sep 24, 2008, at 10:24 AM, Peter Johansson wrote:
John Richetta wrote:
(I'm an autotools newbie.)
What is the automake sanctioned way of providing different top-
level make targets, that build my application with different options?
For example, say I want to build foo_nondebug,
John Richetta wrote:
(I'm an autotools newbie.)
What is the automake sanctioned way of providing different top-level
make targets, that build my application with different options?
For example, say I want to build foo_nondebug, and foo_debug, and
(luckily) all of my application code resides
Hi Ben,
* Ben Pfaff wrote on Wed, Sep 24, 2008 at 06:51:14PM CEST:
Ralf Wildenhues [EMAIL PROTECTED] writes:
I'd really hate to invade make's namespace. They may come up with this
really cool new makefile variable, and we can't use it then. :-/
I wonder whether this is a real issue,
