Re: AM_SUBST_IGNORE = AC_SUBST without Makefile variable definition

2005-10-19 Thread Ralf Wildenhues
[ removed automake-patches, its readers are likely to read here, too, and this isn't about a patch ] Hi Stepan, * Stepan Kasal wrote on Wed, Oct 19, 2005 at 01:37:22PM CEST: > On Wed, Oct 19, 2005 at 11:32:37AM +0200, Ralf Wildenhues wrote: > > I believe what Stepan meant was: *snip* > > not e

Re: Using Variables in *_SOURCES

2005-10-19 Thread Stepan Kasal
Hello, On Wed, Oct 19, 2005 at 09:14:19PM +, Seth Greenfield wrote: > Hello, > I understand that you cannot place any type of > variable in a _SOURCES variable. I think you can: COMMON = ... foo_SOURCES = $(COMMON) foo.c bar_SOURCES = $(COMMON) bar.c HTH, Stepan Kasal

Using Variables in *_SOURCES

2005-10-19 Thread Seth Greenfield
Hello, I understand that you cannot place any type of variable in a _SOURCES variable. My problem is that I have multiple applications which compile code from a common code base. However, I cannot create a library of this common code, because the code makes references to the individual applic

Doing something just a bit more complex than `make check'

2005-10-19 Thread Roberto Bagnara
Hi there, I am using the `make check' facility offered by Automake. However, I need to realize something just a bit more complex than this. What I need to have is a way to specify that the ordinary behavior of `make check' should be repeated a number of times, each time with a different choice

Re: using VPATH in depend2.am?

2005-10-19 Thread Harald Dunkel
Hi folks, Ralf Wildenhues wrote: > > What exactly does not work for you? I tried to use VPATH = $(srcdir):$(top_srcdir)/some/common/dir in Makefile.am. > In what circumstances? I am not sure what you mean by "circumstances". I am trying to build a C++ library (no libtool) using bot

Re: AM_SUBST_IGNORE = AC_SUBST without Makefile variable definition

2005-10-19 Thread Stepan Kasal
Hello, On Wed, Oct 19, 2005 at 11:32:37AM +0200, Ralf Wildenhues wrote: > I believe what Stepan meant was: > If the status.m4 code encounters [EMAIL PROTECTED]@@\n@', where `FOO' has > been > AC_SUBSTed, then treat the replacement of the complete string > [EMAIL PROTECTED]@@\n@' in a special way

Re: AM_SUBST_IGNORE = AC_SUBST without Makefile variable definition

2005-10-19 Thread Ralf Wildenhues
Hi Simon, Stepan, * Simon Richter wrote on Wed, Oct 19, 2005 at 08:53:55AM CEST: > Stepan Kasal schrieb: > > > AC_SUBST([FOO], ["foo > > bar"]) > > Automake could generate lines like this: > > > FOO = @FOO@@\n@ > > There are a lot of cases, in fact, the majority, where the substituted > strin

Re: AM_SUBST_IGNORE = AC_SUBST without Makefile variable definition

2005-10-19 Thread Stepan Kasal
Hello, On Wed, Oct 19, 2005 at 08:53:55AM +0200, Simon Richter wrote: > Stepan Kasal schrieb: > > FOO = @FOO@@\n@ > > There are a lot of cases, in fact, the majority, where the substituted > string is only known at configure time, when the Makefile.in files have > long been generated. of course.

Re: AM_SUBST_IGNORE = AC_SUBST without Makefile variable definition

2005-10-19 Thread Simon Richter
Hi Stepan, Stepan Kasal schrieb: > AC_SUBST([FOO], ["foo > bar"]) [...] > Automake could generate lines like this: > FOO = @FOO@@\n@ There are a lot of cases, in fact, the majority, where the substituted string is only known at configure time, when the Makefile.in files have long been generat