Re: [Patch] Testing loads of cygwin1.dll from MinGW and MSVC, take3

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: [Patch] Testing loads of cygwin1.dll from MinGW and MSVC, take3

Christopher Faylor-2
On Fri, Jun 10, 2005 at 01:13:59PM -0400, Christopher Faylor wrote:
>On Fri, Jun 10, 2005 at 06:11:38PM +0100, Dave Korn wrote:
>>Look, if it's getting complicated and tricky, that argues for a bit of
>>a rethink / redesign, doesn't it?
>
>Yes.  I was wondering why we were going down this path when we've both
>noted that maybe it wasn't a good idea.
>
>I would still prefer a generic "mingw" solution which is integrated with
>the rest of the test suite.

I thought waiting six months for this solution was probably long enough
so I've implemented something like this in the current test suite.  So,
after moving stuff out of the cygload directory and into the winsup.api
directory, this means that cygload is run during the normal execution of
the test suite rather than as a separate step.

cgf