Jeffrey Walton writes:
I'm having this problem on 32-bit ARM:
https://stackoverflow.com/q/33474070/608639
That describes a different problem than the one you are describing here.
Our bin_* recipe looks like this:
bin_PROGRAMS = cryptest
cryptest_CXXFLAGS = $(AM_CXXFLAGS)
cryptest_SOURCES =
Harlan Stenn writes:
Stefano Lattarini writes:
> My suggestion: if files in different subdirectories are actually
> dependent on each other (that is, the subdirectories are not
> really independent "modules" that can be built independently and
> oblivious to each other), re-organize your build s
Consider automake being used together with GNU make and autoconf.
Top level directory 'main'. Two subdirectories, 'a' and 'b'.
main/configure.ac
AC_CONFIGFILES([
...
a/somefile.inc
...
])
main/Makefile.am:
SUBDIRS=a b
main/a/Makefile.am:
data_DATA=somefile.inc
DISTCLEAN=somefile.inc
ma
Too, Justin A. writes:
Hi Baurzhan,
On 9/20/12 10:52 AM, "Baurzhan Ismagulov" wrote:
>On Thu, Sep 20, 2012 at 10:24:28AM -0700, Too, Justin A. wrote:
>> I would like to build and distribute a pre-built binary package for my
>> project
>
>For which OS / distribution?
For example: Linux (rhel5
Marko Kreen writes:
Antimake already has per-target object files so it should be easy
to add another level of indirection. But I wonder whether it's
actually necessary, as you can always do:
bin_PROGRAMS = foo
noinst_PROGRAMS = foo_debug
foo_SOURCES = ...
foo_C
Marko Kreen writes:
Antimake is my attempt to fix "no good build system" problem -
GNU Make library, but instead inventing custom conventions,
it implements Automake syntax.
Example:
bin_PROGRAMS = hello
hello_SOURCES = hello.c
include antimake.mk
After writing such Makefile, you can r
Stefano Lattarini writes:
A quick workaround to obtain this behaviour is to write your custom/rules
defintion in a `.am' fragment in your source tree, and then include it
from all the Makefile.am files that need it:
$ cat my-rules.am
my_variable = ...
.ctpl.c:
# rules to create a
I'm looking for a way to implement an optional plugin-like facility in
automake.
Basically, take a stock distro installation of automake, then augment it
somehow so that automake would add my stuff into each Makefile.in file that
it generates from Makefile.am.
My situation is that I'm ins
