Re: _SHORTNAME in conditional

On 6 January 2016 at 06:01, Thomas Martitz wrote: > Am 05.01.2016 um 23:41 schrieb Gavin Smith: >> On 5 January 2016 at 21:05, Thomas Martitz wrote: >>> Automake source code is a myth to me, I wasn't able to find the code that >>> implements this limitation

Re: _SHORTNAME in conditional

Hi, I've written an RFC patch that solves my root problem so that I wouldn't have to use _SHORTNAME at all. Please have a look at that and comment on it! I'll still follow-up with my findings regarding _SHORTNAME below. Am 06.01.2016 um 13:15 schrieb Gavin Smith: On 6 January 2016 at

Re: _SHORTNAME in conditional

Am 05.01.2016 um 22:05 schrieb Thomas Martitz: Hello, Given this fragment: bin_PROGRAMS = false true true_SOURCES = false.c true_CFLAGS = -DAM_TRUE true_SHORTNAME = t if FOO false_SOURCES = false.c false_CFLAGS = -DAM_FALSE false_SHORTNAME = f endif I receive a warning for false_SHORTNAME:

Re: _SHORTNAME in conditional

Am 05.01.2016 um 23:41 schrieb Gavin Smith: > On 5 January 2016 at 21:05, Thomas Martitz wrote: >> Automake source code is a myth to me, I wasn't able to find the code that >> implements this limitation (only the place where the warning is printed >> (variable_value() =>

_SHORTNAME in conditional

Hello, Given this fragment: bin_PROGRAMS = false true true_SOURCES = false.c true_CFLAGS = -DAM_TRUE true_SHORTNAME = t if FOO false_SOURCES = false.c false_CFLAGS = -DAM_FALSE false_SHORTNAME = f endif I receive a warning for false_SHORTNAME: Makefile.am:9: warning: automake does not support