I'm looking for a structure like this to work:
src/Makefile.am
---
include foo/frag1.mk
src/foo/frag1.mk
include frag2.mk
src/foo/frag2.mk
some stuff
But at the moment (automake 1.11.1) the notion of current directory when
processing foo/frag2.mk is
On Sunday, August 1, Ralf Wildenhues wrote:
> Sure. I have no idea yet how exactly this could work in
> practice. I don't know these tools yet. I'm just
> throwing out these ideas to see if somebody has good
> input.
>
> In such a project, is there any scripting besides CMD that
> one could r
On Saturday, July 31, 2010, Ralf Wildenhues wrote:
> * David Byron wrote on Sat, Jul 31, 2010 at 10:41:29PM CEST:
>
> > If someone is running autotools (or even a generated
> > configure script) on windows, I think we can assume
> > they've either got cygwin or msy
On Saturday, July 31, 2010, Ralf Wildenhues wrote:
> Here's a crazy idea: how about if automake optionally
> output an input file suitable for nmake (after configure
> substitution)? Is that even feasible? (I'd guess so)
> Maybe if we have contents conditional on 'make' or 'nmake'
> output? Wou
> Here's a ping for Ralph.
I asked for his help and then I went and spelled his name wrong. My
apologies Ralf.
-DB
On Friday September 4th, 2009, Eric Blake wrote:
> According to David Byron on 8/14/2009 1:57 PM:
>
> > I'm not sure whether this is something I'm doing wrong
> > or something wrong with automake, autoconf or libtool.
> > At the moment I'm leaning
On Saturday, January 27, 2007 @ 7:52a, Ralf Wildenhues wrote:
> Surely writing libfoo.a is a problem when using MSVC + LIB for archive
> creation. But then again that doesn't work well out of the
> box anyway;
> you could be using Libtool, name it libfoo.la and put -static in
> libfoo_la_LDFLAGS
I'm trying to conditionally add a program-specific linker flag but I'm
having trouble.
Part of my Makefile.am looks like this:
noinst_PROGRAMS = zombie immOutTester testrunner
# Use these flags for all the programs built here
LDADD = $(top_builddir)/util/util.a $(BOOST_LIBS) ${PTHREAD_LIBS}
# t
On Wednesday, January 17th, 2007 @ 10:37a, Brian Dessent wrote:
> David Byron wrote:
>
> > /usr/share/aclocal/libsmi.m4:8: warning: underquoted
> > definition of AM_PATH_LIBSMI
> >
> > /usr/share/aclocal/libmcrypt.m4:17: warning: underquoted
> > definition of
I'm not sure whether this is a cygwin problem, an automake problem, or my
problem but I thought I'd start here.
I'm trying to run the autotools on cygwin (eventually using cccl when I get
that far), but I'm running into trouble before that. Here's the error I
get:
$ autoreconf -fvi
autoreconf-2.
On Monday, January 8, 2007 @ 11:46a, Ralf Wildenheus wrote:
> * David Byron wrote on Mon, Jan 08, 2007 at 08:25:28PM CET:
> > On Monday, January 8 @ 11:05a, Ralf Wildenhues wrote:
> > > * David Byron wrote on Mon, Jan 08, 2007 at 07:40:02PM CET:
> [...]
> > > >
On Monday, January 8 @ 11:05a, Ralf Wildenhues wrote:
> Hello David,
>
> * David Byron wrote on Mon, Jan 08, 2007 at 07:40:02PM CET:
> > I'm having trouble getting a .deps directory generated when
> I think it
> > should. As a result, I see this error:
I'm having trouble getting a .deps directory generated when I think it
should. As a result, I see this error:
Makefile:357: .deps/TestECVersion.Po: No such file or directory
I don't think I'm doing anything particularly complicated.
My directory structure looks like this:
agent
config/
tes
On Sat, Jul 29, 2006, Stepan Kasal wrote:
> On Fri, Jul 28, 2006 at 12:20:29PM -0700, David Byron wrote:
>
> > I tried _AM_SUBST_NOTMAKE, but I see the following error:
> >
> > configure.ac:212: error: possibly undefined macro: _AM_SUBST_NOTMAKE
>
> I'm a
> indeed, multiline variables do not work with Automake.
> In a future release, the substituted multiline value should be
> escaped by default, so that the resulting makefile works correctly.
Good news.
> In the meantime, there is a workaround available: use the
> undocumented macro _AM_SUBST_NOT
Pretty sure this is both an automake and autoconf question, but somehow it
seems like the automake list is the place to start.
I just unwrapped a fresh copy of autoconf 2.60 to take advantage of
multiline variables in AC_SUBST. I really only want the values to appear in
C code, not in Makefiles.
I've got a couple of distclean-related questions. I'm using automake 1.9.6.
My setup is like this:
foo
foo/testsuite
where both foo and foo/testsuite contain Makefile.am. The Makefile.am in
foo contains
DIST_SUBDIRS = testsuite
foo also contains configure.ac which says among other things:
A
On Monday, May 08, 2006 Ralf Wildenhues wrote:
> If you're going to merge the Makefile.am's, or include one
> into the other, be sure to do the configure.ac merge first.
Your post just got this to sink in for me. I was trying to keep the
configure.ac's separate since it felt better to have th
Not sure if this is more automake or autoconf related.
I'm fairly early in the process of creating one top level
Makefile.am/configure.ac to get non-recursive Makefiles. I've got a few
directories already building with autoconf/automake. I'm using
AC_CONFIG_SUBDIRS at the moment so configure sti
On November 24, 2005, Ralf wrote:
> > My original two cases were:
> >
> > 1. ACLOCAL_AMFLAGS = -I ../../scripts/m4
>
> which pointed outside your package and thus is a nono (do
> not specify relative paths which point to something outside
> of your package).
>
> > or
> >
> > 2. ACLOCAL_AMFLAGS
On November 17, 2005, Ralf wrote:
> * David Byron wrote on Wed, Nov 16, 2005 at 04:37:45PM CET:
> > On November 15, 2005, Ralf wrote:
> >
> > > First idea: In the directory, where aclocal searches by
> > > default ($prefix/share/aclocal, usually), edit/create the
On November 15, 2005, Ralf wrote:
> First idea: In the directory, where aclocal searches by
> default ($prefix/share/aclocal, usually), edit/create the
> file `dirlist' to point to the directory your macros are in.
> Then, #2 will work without any ACLOCAL_AMFLAGS.
I could see this working, but th
I've defined some macros that I'd like to share across projects. Seems
to me I've got two choices for getting them in my dist tarball:
1. include the macros I wrote in the files I wrote
2. include the macros I wrote in aclocal.m4
>From what I can tell, automake chooses #1 when ACLOCAL_AMFLAGS is
On Friday, November 4th, Ralf Wildenhues wrote:
> Can't you just make it depend on the other source files?
>
> builddate.c: $(geoidx_SOURCES)
> echo ...
>
> Don't forget to mention the header file somewhere, by the
> way (in geoidx_SOURCES would be fine).
I could, but what about any
This feels like a faq, but I couldn't find anything related so here
goes.
I'd like to compile in the build time into my application. I have a
recipe like this:
BUILDTIME = $(shell TZ=UTC date --utc)
builddate.c:
echo "#include " >$@
echo >>$@
echo "const char *BuildDate
25 matches
Mail list logo
