Re: test setup advice

Hi Tom, tom fogal wrote: I'm looking for advice on how to structure a build system using automake. Thanks for any solutions / ideas / comments. -tom These are just random thoughts / ideas that I used on C++ projects, just my two cents (and in all cases, my personal opinion, your mileag

Re: test setup advice

Hi Tom, * tom fogal wrote on Wed, Mar 29, 2006 at 05:20:18AM CEST: > Ralf Wildenhues writes: > >Does that help? > > Its an order of magnitude better than what I've got now certainly. > What I'd really like to see is a program which parses tests/*cpp and > generates >test1_SOURCES=../src/abc.

Re: Partial linking with _RELOCATABLES - Proposed enhancement (revised and commented)

Hi Alexandre and All, Alexandre Duret-Lutz wrote: I didn't know "ld -r". How portable is it? The command might be named differently per architecture/OS, but I the concept exist on all platforms that I know of (called incremental linking, or partial linking). "ld -r" as is can be found

Re: test setup advice

<[EMAIL PROTECTED]>Ralf Wildenhues writes: >Hi Tom, Hi! >* tom fogal wrote on Mon, Mar 27, 2006 at 11:17:51PM CEST: >> My /tests directory then uses that same `everything' library to link >> all of the test programs against. However the build trees for /src and >> /tests are separate; the topl

Re: output directory of generated files

Am Tue, 28 Mar 2006 15:36:36 +0200 schrieb Stepan Kasal <[EMAIL PROTECTED]>: > Hello, > > On Thu, Mar 09, 2006 at 02:48:13PM +0100, Thomas Porschberg wrote: > > %.qm: %.ts > > $(PROG1) $< > > > > foo.h: foo.qm > > $(top_srcdir)/utils/PROG2 < $< > $@ > ... > > PROG2 expected foo.q

Re: output directory of generated files

Hello, On Thu, Mar 09, 2006 at 02:48:13PM +0100, Thomas Porschberg wrote: > %.qm: %.ts > $(PROG1) $< > > foo.h: foo.qm > $(top_srcdir)/utils/PROG2 < $< > $@ ... > PROG2 expected foo.qm now in BUILDDIR/src and not under project/src/. > (surprisingly it worked when I started make a

Re: BUILT_SOURCES: dependencies not copied to build_dir

Hello, On Tue, Mar 28, 2006 at 12:16:18PM +0200, Michael Biebl meant to write: > EXTRA_DIST = ngcs_marshal.ngci idef.py ngcs.py > CLEANFILES = ngcs_marshal.h ngcs_marshal.c > > ngcs_marshal.c: ngcs_marshal.ngci idef.py > $(srcdir)/idef.py $(srcdir)/ngcs_marshal $@ > > ngcs_marshal.h: ngc

Re: BUILT_SOURCES: dependencies not copied to build_dir

Ralf Wildenhues wrote: > Hi Michael, > > * Michael Biebl wrote on Tue, Mar 28, 2006 at 12:16:18PM CEST: >> This is the solution I came up with: >> >> EXTRA_DIST = ngcs_marshal.ngci idef.py ngcs.py >> CLEANFILES = ngcs_marshal.h ngcs_marshal.c >> >> ngcs_marshal.c: ngcs_marshal.ngci idef.py >>

Re: BUILT_SOURCES: dependencies not copied to build_dir

Hi Michael, * Michael Biebl wrote on Tue, Mar 28, 2006 at 12:16:18PM CEST: > This is the solution I came up with: > > EXTRA_DIST = ngcs_marshal.ngci idef.py ngcs.py > CLEANFILES = ngcs_marshal.h ngcs_marshal.c > > ngcs_marshal.c: ngcs_marshal.ngci idef.py > $(srcdir)/idef.py $(srcdir)/ng

Re: BUILT_SOURCES: dependencies not copied to build_dir

Ralf Wildenhues wrote: > Hi Michael, Tom, Hi, thanks for you help so far. > * tom fogal wrote on Mon, Mar 27, 2006 at 10:38:27PM CEST: >> <[EMAIL PROTECTED]>Michael Biebl writes: >> >>> ngcs_marshal.c: ngcs_marshal.ngci idef.py >>>$(srcdir)/idef.py ngcs_marshal >>> >>> ngcs_marshal.h:

Re: BUILT_SOURCES: dependencies not copied to build_dir

Hi Michael, Tom, * tom fogal wrote on Mon, Mar 27, 2006 at 10:38:27PM CEST: > <[EMAIL PROTECTED]>Michael Biebl writes: > > >ngcs_marshal.c: ngcs_marshal.ngci idef.py > >$(srcdir)/idef.py ngcs_marshal > > > >ngcs_marshal.h: ngcs_marshal.ngci idef.py > >$(srcdir)/idef.py ngcs_marsh

Re: test setup advice

* Ralf Wildenhues wrote on Tue, Mar 28, 2006 at 09:59:26AM CEST: > TESTS = $(check_PROGRAMS) > check_PROGRAMS = tests/a$(EXEEXT) tests/b$(EXEEXT) tests/c$(EXEEXT) I should add that the $(EXEEXT) are not necessary with CVS Automake any more. They were never necessary for *_PROGRAMS, but for TESTS