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
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.
<[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
* 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
Hi Tom,
* tom fogal wrote on Mon, Mar 27, 2006 at 11:17:51PM CEST:
>
> I'm writing a C++ project which I currently have just under 30
> automake-based tests (e.g. check_PROGRAMS, TESTS) created. The
> structure of my build system is that all of my source files for the
> program (under /src) buil
I'm looking for advice on how to structure a build system using
automake.
I'm writing a C++ project which I currently have just under 30
automake-based tests (e.g. check_PROGRAMS, TESTS) created. The
structure of my build system is that all of my source files for the
program (under /src) build a
