autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How do I conditinally make a makefile?


From: Andreas Schwab
Subject: Re: How do I conditinally make a makefile?
Date: Fri, 19 Apr 2002 23:10:47 +0200
User-agent: Gnus/5.090005 (Oort Gnus v0.05) Emacs/21.2.50 (ia64-suse-linux)

"Thomas E. Dickey" <address@hidden> writes:

|> On Fri, 19 Apr 2002, Andreas Schwab wrote:
|> 
|> > "Thomas E. Dickey" <address@hidden> writes:
|> >
|> > |> On Fri, 19 Apr 2002, Andreas Schwab wrote:
|> > |>
|> > |> > |> If you really want to do this you could use a shell variable:
|> > |> > |>
|> > |> > |> makefiles="$makefiles Makefile.maybe"
|> > |> > |>
|> > |> > |> AC_OUTPUT($makefiles)
|> > |> >
|> > |> > Better yet, use AC_CONFIG_FILES.  Calling AC_OUTPUT with argument is
|> > |> > considered obsolete usage.
|> > |>
|> > |> only by people who prefer to misuse the terms (what you should say, to 
be
|> > |> accurate is that autoconf 2.5x is designed to be incompatible in this
|> > |> area)
|> >
|> > In which way is it incompatible?
|> 
|> aside from bugs?  2.53 has some new ones which I noticed but haven't
|> gotten around to studying - I only got to that early this week.
|> 
|> The usual point about incompatibility is that quoting has changed.

I haven't seen a case where inserting a pair of quotes that is now needed
by 2.5x breaks the script for 2.13.  The old version was just less strict
about them, but it was wrong anyway.

Andreas.

-- 
Andreas Schwab, SuSE Labs, address@hidden
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."



reply via email to

[Prev in Thread] Current Thread [Next in Thread]