Re: vpath builds and nobase_include_HEADERS

2009-06-03 Thread Ralf Wildenhues
Just because I think my reply is easily misunderstood: * Ralf Wildenhues wrote on Thu, Jun 04, 2009 at 07:47:50AM CEST: > * johnwohlb...@gmail.com wrote on Thu, Jun 04, 2009 at 12:24:29AM CEST: > > > > from lib1/Makefile.am > > > > nobase_include_HEADERS = \ > > $(header_file_list) > > The above

Re: vpath builds and nobase_include_HEADERS

2009-06-03 Thread Ralf Wildenhues
Hello John, * johnwohlb...@gmail.com wrote on Thu, Jun 04, 2009 at 12:24:29AM CEST: > I'm having troubles with out of tree (vpath) builds, using > nobase_include_HEADERS, and *.in files processed by configure. I think you're making things more complicated than they need to be. > I have a colle

Re: running tests under in a tests/ directory

2009-06-03 Thread Ralf Wildenhues
* aaragon wrote on Wed, Jun 03, 2009 at 09:22:59PM CEST: > Ralf Wildenhues wrote: > > * aaragon wrote on Sat, May 30, 2009 at 07:34:13PM CEST: > >> check:all > >> @echo "Running tests" > >> cd $(TSTDIR) && $(MAKE) $(AM_MAKEFLAGS) -s test > >> Except that if I change 'check: all

Re: running tests under in a tests/ directory

2009-06-03 Thread aaragon
Hi Ralph, thanks again for replying. Ralf Wildenhues wrote: > > Hello Alejandro, > > * aaragon wrote on Sat, May 30, 2009 at 07:34:13PM CEST: >> >> Thank yo Ralf for replying to my post. The code that I showed in my post >> was >> indeed taken from that website. The code you provided me is w

vpath builds and nobase_include_HEADERS

2009-06-03 Thread johnwohlbier
I'm having troubles with out of tree (vpath) builds, using nobase_include_HEADERS, and *.in files processed by configure. I have a collection of components in a component library. src/ src/lib1/ Makefile.am header1.hh types.hh.in source1.cc src/lib2/ Makefile.am header2.hh source2.cc I want t

Re: running tests under in a tests/ directory

2009-06-03 Thread Ralf Wildenhues
Hello Alejandro, * aaragon wrote on Sat, May 30, 2009 at 07:34:13PM CEST: > > Thank yo Ralf for replying to my post. The code that I showed in my post was > indeed taken from that website. The code you provided me is way too advanced > for me, since I consider myself just a user. The main idea th