Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Fri, 1 Sep 2000 08:53:24 -0400 Message-Id: <200009011253.IAA17108@envy.delorie.com> From: DJ Delorie To: deo AT logos-m DOT ru CC: cygwin-developers AT sources DOT redhat DOT com In-reply-to: <106339243866.20000901110237@logos-m.ru> (message from Egor Duda on Fri, 1 Sep 2000 11:02:37 +0400) Subject: Re: testsuite References: <20000831165024 DOT A15210 AT cygnus DOT com> <200008312055 DOT QAA25395 AT envy DOT delorie DOT com> <20000831170237 DOT B15144 AT cygnus DOT com> <200008312122 DOT RAA25605 AT envy DOT delorie DOT com> <106339243866 DOT 20000901110237 AT logos-m DOT ru> > DD> You don't need Makefiles all over the testsuite. In fact, there are > DD> *no* makefiles in the existing cygwin testsuite. > > yes, because all needed support is built as part of winsup/cygwin/ > build. but now i need to build yet another support lib. the question I didn't say you *couldn't* have a Makefile. I just said they weren't required. Certainly, if you need to do some pre-builds for "make check", go ahead and add a Makefile and hook it into winsup's "make check" rule (which doesn't yet exist).