[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Removing the non trace based code
From: |
Akim Demaille |
Subject: |
Re: Removing the non trace based code |
Date: |
06 Nov 2001 12:38:49 +0100 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Artificial Intelligence) |
>>>>> "adl" == Alexandre Duret-Lutz <address@hidden> writes:
>>>> "Akim" == Akim Demaille <address@hidden> writes:
Akim> I am willing to remove the non trace based code from Automake.
Akim> Is there any body would fear this?
Akim> There is one single issue: people who still use LIBOBJ
Akim> assignments instead of AC_LIBOBJ will have bad surprises. But
Akim> this is a task for Autoconf, not for Automake.
adl> Do you mean you want to warn about user LIBOBJS assignments in
adl> Autoconf (say by using some special comment after the assignment
adl> and grepping the configure output for assignments that don't have
adl> it) and require this new version of Autoconf from Automake?
I plan to have all the occurrences of LIBOBJ from Autoconf rewritten
as LIB@&address@hidden, and m4_pattern_forbid ^LIBOBJ$ (with a specific
message). The only problem I see are the places where LIBOBJ is
*read*, such as in the traditional LTLIBOBJ declaration.
adl> Or do you simply want to put a big warning in the NEWS?
Indeed.
adl> Something else?
Ideas are welcome.
adl> (BTW does autoupdate handles this?)
Nope. And it cannot :(