automake-patches
[Top][All Lists]
Advanced

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

Re: superfluous link rule for unknown languages


From: Tom Tromey
Subject: Re: superfluous link rule for unknown languages
Date: 18 Jul 2001 19:20:07 -0600

>>>>> "Tim" == Tim Van Holder <address@hidden> writes:

Tim> I think the idea is to always add $(EXEEXT); whenever autoconf
Tim> sets up compilation for some language, EXEEXT is deduced.

This isn't backwards compatible.  With autoconf 2.13, EXEEXT is never
set.  So we can't define it in Makefile.in.

Tim> Except of course if, like in the bug report, it's a custom
Tim> compilation; then automake should probably indeed recognize
Tim> 'foo:' as the custom rule if bin_PROGRAMS contains 'foo'.  I
Tim> doubt very much that many packages would rely on 'foo' being a
Tim> rule in addition to foo$(EXEEXT) - after all, if such a rule
Tim> existed, it would cause substantially different behaviour on
Tim> systems with and without executable extensions.

Suppose the maintainer uses `foo:' as the custom rule.
Then the user tries to build on Windows.
The build fails because there is no rule for `foo.exe'.

We could make a special case here (don't make the foo$(EXEEXT) target
if we see `foo') and just hope that doesn't happen.

The other question is how and when to define EXEEXT.
One idea is to hook it to AC_PROG_CC/CXX via hackery in
AM_INIT_AUTOMAKE.  That is, make it mandatory just like it is in
autoconf 2.50.

Right now I don't have another idea.

Tom



reply via email to

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