[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ${OBJEXT} in implicit rule
|
From: |
Jan Engelhardt |
|
Subject: |
Re: ${OBJEXT} in implicit rule |
|
Date: |
Wed, 12 Nov 2014 21:53:36 +0100 (CET) |
|
User-agent: |
Alpine 2.11 (LSU 23 2013-08-11) |
On Wednesday 2014-11-12 20:15, Nick Bowler wrote:
>On 2014-11-12 16:58 +0100, Jan Engelhardt wrote:
>> Using automake-1.13.4, when using the following Makefile.am fragment,
>> .k.${OBJEXT}:
>> gcc -x c -c $< -o $@
>> I observe that bar.o is not built and not linked into foo.
>
>Indeed, the use of custom file extensions in _SOURCES seems to be
>completely borken. [...]
>I didn't even know this was a feature at all, but sure enough it's
>documented[1]. [...]
>I suggest ignoring this functionality entirely, because the sane way to
>add custom compiler rules is to use _LDADD or _LIBADD.
Heh, I just came from _LDADD and EXTRA_DIST, because that
was not documented. _SOURCES was.
I do not mind which way, but something should be fixed —
either the automake program, or its documentation :)