[Patch] Testing loads of cygwin1.dll from MinGW and MSVC, take 3

Christopher Faylor cgf-no-personal-reply-please@cygwin.com
Tue Jun 7 16:22:00 GMT 2005


On Tue, Jun 07, 2005 at 05:10:16PM +0100, Dave Korn wrote:
>----Original Message----
>>From: Christopher Faylor
>>Sent: 07 June 2005 00:52
>>On Mon, Jun 06, 2005 at 04:11:32PM -0700, Max Kaehn wrote:
>>>On Mon, 2005-06-06 at 16:07, Igor Pechtchanski wrote:
>>>>I take it you meant
>>>>
>>>>-       $(RUNTEST) --tool winsup $(RUNTESTFLAGS) ;\
>>>>+       $(RUNTEST) --tool winsup $(RUNTESTFLAGS) &&\
>>>
>>>Oh, right, this is the world of shell scripts, not C.  Thanks for
>>>catching that.
>>
>>Actually neither is right.  The tests are supposed to run to
>>completion, not stop on a failure.
>
>I'm of the opinion that cygload should be a subdirectory of
>winsup/testsuite/winsup.api, since it's a functionality of the winsup
>api that's being tested here, not an entire new tool.

I think you're right.  I checked this in just to get something that we
could play with.  I thought that we'd move this around a little
eventually.

What might make sense is to either have a "mingw" directory where
targets are built with '-mno-cygwin' or to adopt a convention that files
with the name '-mingw' are built with '-mno-cygwin'.

Brian could possibly use something like that for his SYSTEMROOT test.

cgf



More information about the Cygwin-patches mailing list