Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Thu, 31 Aug 2000 16:55:34 -0400
Message-Id: <200008312055.QAA25395@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: cgf AT cygnus DOT com
CC: cygwin-developers AT sources DOT redhat DOT com
In-reply-to: <20000831165024.A15210@cygnus.com> (message from Chris Faylor on
	Thu, 31 Aug 2000 16:50:24 -0400)
Subject: Re: testsuite
References:  <20000831165024 DOT A15210 AT cygnus DOT com>


The rule is, as best I can tell, this structure:

* the directory where the makefile has "make check" capability,
* subdirectory testsuite
* subdirectories package.*
* optionally more subdirectories
* files *.exp

If you changed winsup/Makefile.in to support "make check" then there
would have to be src/winsup/testsuite/*/*.exp

Note: you can have *more* subdirectories under testsuite/package.*,
but not *less*.

So, this would be feasible:

src/winsup
	testsuite
		cygwin.*
			winsup.api/winsup.exp (etc)
		w32api.*
		mingw.*

Personally, I'd prefer the testsuites under the packages, but that's
just to keep the mess localized.