Subject: Re: Building multiple progs from a single directory
To: Julio M. Merino Vidal <email@example.com>
From: David Laight <firstname.lastname@example.org>
Date: 07/08/2007 20:12:39
On Sun, Jul 08, 2007 at 05:34:54PM +0200, Julio M. Merino Vidal wrote:
> [ Please CC me any replies ]
> [ CCing Marting because he is my SoC mentor ]
> It seems to me that keeping
> each test program in its own directory will be overkill, given that
> test programs should be fine-grained and thus there will be many of
Are you sure that multiple test programs is the way to go?
You'll almost certainly end up with a lot of replicated and/or
red tape code that makes the actual test difficult to see.
Any changes to the infrastucture will then need making to every clone
of the test program.
Certainly you want to be also to run each test separately, but that
doesn't require one program per test.
> Following the current principle of one program per source directory
> will make our source tree explode in the number of required inodes to
> host it -- an extra Makefile plus a directory for each of these tiny
Given the extra directories (etc) would be subdirectories of a single
program why is this an issue?
You'll end up with more inodes used for the objects and programs anyway.
> My bsd.test.mk file is built on top of bsd.prog.mk file for
> simplicity (and because I see no reason to do it otherwise).
Did you look at the existing regression tests ?
> In order to get the above to work, I have adapted our bsd.prog.mk file
> to support building several different programs in the same directory.
My view is that these makefiles are too complicated already (yes I have
modified them myself) and that this adds complexity that isn't needed.
David Laight: email@example.com