Hi Ed,
* E. Rosten wrote on Mon, May 23, 2005 at 06:59:05PM CEST:
Based on my recent experience of learning to write autoconf for a new
library, I have written a brief autoconf tutorial which should be able to
get people in to a state where they can start hacking. Everything
Hi Ed,
Please keep the mailing list copied, this is interesting for others as
well. Thank you.
* E. Rosten wrote on Wed, May 25, 2005 at 10:53:13AM CEST:
On Wed, 25 May 2005, Ralf Wildenhues wrote:
* E. Rosten wrote on Mon, May 23, 2005 at 06:59:05PM CEST:
| M4 arguments are quoted with [
Hello, Ed!
There are many things that are considered bad practice. There are
many things that are old deprecated ways to do things.
For example, using the file name configure.in is outdated. You should
use configure.ac.
I guess (I don't really know) that the reason for this is that in is
On Thu, 2005-05-26 at 09:59 +0900, Andre Caldas wrote:
Hello, Ed!
There are many things that are considered bad practice. There are
many things that are old deprecated ways to do things.
For example, using the file name configure.in is outdated. You should
use configure.ac.
On 5/23/05, E. Rosten [EMAIL PROTECTED] wrote:
Based on my recent experience of learning to write autoconf for a new
library, I have written a brief autoconf tutorial which should be able to
get people in to a state where they can start hacking.
This was very helpful. Thank you for posting
On Tue, May 24, 2005 at 12:48:13AM -0700, Travis Spencer wrote:
On 5/23/05, E. Rosten [EMAIL PROTECTED] wrote:
Based on my recent experience of learning to write autoconf for a new
library, I have written a brief autoconf tutorial which should be able to
get people in to a state where
Dear all,
Based on my recent experience of learning to write autoconf for a new
library, I have written a brief autoconf tutorial which should be able to
get people in to a state where they can start hacking. Everything is
accompanied by a short, but working configure.in example.
It's here
