Hello,
my name is Thomas Martitz and I'd say quite knowledgeable with automake.
However I've hit a road block that I'm unable to resolve. I'm also new
to this list, so please bear with me.
I'm trying to port a project to non-recursive automake following[1]. I
have c
The make target refers to a directory (trailing slash). I suspect the
Makefile.am has a typo.
Am 21. September 2015 17:21:46 MESZ, schrieb Bob Friesenhahn
:
>On Mon, 21 Sep 2015, Arthur Schwarz wrote:
>
>>
>>
>> I'm trying to use LDADD to reference libgslip.a in another directory.
>After
>> bui
Am 01.12.2015 um 13:44 schrieb R. Diez:
Hi Automake devs:
I need to build some files outside of the build repository, and I
cannot use option 'subdir-objects' because of an Automake bug, so I
constantly get many warnings like this with newer Automake versions:
warning: source file '$(BLAH_
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 f
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
>>
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
This option is intended to be used in conjunction with subdir-objects and
Automake-time substitutions for included makefile fragments (%C%, %D%). It
suppresses the generation path components in object filenames.
It should equivalent to setting %C%_foo_SHORTNAME=foo, except it can work if
the makef
This option is intended to be used in conjunction with subdir-objects and
Automake-time substitutions for included makefile fragments (%C%, %D%). It
suppresses the generation path components in object filenames.
It should equivalent to setting %C%_foo_SHORTNAME=foo, except it can work if
the makef
y 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 (only the place where the warning is printed
(varia
Am 08.01.2016 um 16:03 schrieb Gavin Smith:
On 8 January 2016 at 14:33, Gavin Smith wrote:
Failing that, it would be better for conditional SHORTNAME to work,
instead of adding a new option.
For example:
--- automake-orig 2016-01-08 14:54:04.0 +
+++ /home/g/local/bin/automa
Am 08.01.2016 um 16:55 schrieb Gavin Smith:
On 6 January 2016 at 09:17, Thomas Martitz wrote:
It should equivalent to setting %C%_foo_SHORTNAME=foo, except it can work if
the makefile fragment is conditionally included, which improves the modularity
of Automake-using projects.
Example
This option is intended to be used in conjunction with subdir-objects and
Automake-time substitutions for included makefile fragments (%C%, %D%). It
suppresses the generation path components in object filenames.
It should equivalent to setting %C%_foo_SHORTNAME=foo, except it can work if
the makef
Hello,
I know there is no currently active maintainer. However, there is an
important bug fix in the current git, and I've postet a patch for review
that I really need for my projects.
Is there any possibility that my patch can be reviewed and merged, and
that one more release can happen, ev
Am 07.09.2016 um 10:02 schrieb Bent Bisballe Nyeng:
Hi list
Sorry for cross-posting. I originally posted this to the autoconf
list, but after further investigation I have reached the conclusion
that my question is in fact more related to automake.
I have a project in which I include a few ou
Hello,
when transitioning a project to non-recursive Automake, using %reldir%,
you lose the ability to define per-directory AM_{CPP,C,CXX,LD}FLAGS.
With recursive Automake, you can simply set AM_CFLAGS in each
Makefile.am. Attempting the same in a non-recursive setup would modify
the single
Am 14.05.2017 um 14:35 schrieb Mathieu Lirzin:
> Hello,
>
> Thomas Martitz writes:
>>
>> If there are no other solutions, would the above idea considered if
>> someone posted a patch?
>
> I think I understand what you mean, however the issue has nothing to d
Hello,
are there any plans to release Automake 1.16?
Currently, there is still a nasty bug in 1.15 that is fixed in the
development code (I'm talking about the "foo_SOURCES containing
variables like $(srcdir)/foo.c" one). Also, I would like to see a
release that ships my shorter object file n
Hello,
here's some quite annoying warning. I'm trying to define a variable
TEST_LDFLAGS that multiple programs use. There is no program named TEST.
The same works fine with TEST_CFLAGS (i.e. no warning is displayed).
Here's the warning:
Makefile.am:4: warning: variable 'TEST_LDFLAGS' is defi
Am 20.11.2017 um 19:01 schrieb Nick Bowler:
Hi,
If you were to later add a program called TEST, then the results could
be surprising. But you can certainly ignore the warning if you'd like.
I understand that, however we're extremely unlikely to build programs
named in all-upper case.
Alte
Am 25.08.19 um 00:03 schrieb Assaf Gordon:
Issue solved!
Thanks to Bruno Haible in
https://lists.gnu.org/r/bug-gnulib/2019-08/msg00064.html
Quoting that message (and my reply):
---
On 2019-08-24 3:36 p.m., Bruno Haible wrote:
I think the problem is that 'bmake' does not consider the targets
Am 10.12.19 um 22:46 schrieb Georg-Johann Lay:
Will this also work with same file names? Like
avrfoo_LIBRARIES = libfoo.a
avrbar_LIBRARIES = libfoo.a
Should work. The _LIBRARIES suffix causes the file libfoo.a to be built,
the prefix just says install the file (whoever created it) to a sp
21 matches
Mail list logo
