Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com In-Reply-To: <6.0.1.1.0.20040325201031.02854fd8@pop.rcn.com> To: cygwin AT cygwin DOT com MIME-Version: 1.0 Subject: Re: Cygwin under Wine? From: Thomas L Roche Message-ID: Date: Thu, 25 Mar 2004 20:39:16 -0500 Content-Type: text/plain; charset="US-ASCII" At 07:33 PM 3/25/2004, Tom Roche wrote: >>>> While sounding out Cygwin users in my organization, I got the >>>> comment: >>>>> If Cygwin would run under Wine, I'd be a very happy person, we >>>>> wouldn't need real Windows machines for builds, and we could >>>>> consign all our Windows build machines, their ITSC compliance, >>>>> and the continual stream of updates and security fixes to the >>>>> deepest pits of hell. Larry Hall 03/25/2004 07:45:39 PM: >>> I'm not sure I see the logic in the comment from which the >>> question stems. If the goal is to avoid using Windows platforms >>> for builds, why isn't a cross-compiler targeting Windows enough? At 07:59 PM 3/25/2004, Tom Roche wrote: >> For one thing, in these modern times, building usually also >> involves some smoke-, unit- or function-test (i.e. "build >> verification test"). Larry Hall 03/25/2004 08:19:15 PM: > So are you saying that it's not a requirement that your build > environment running under Wine be able to run smoke/unit/function > tests but it would be for a cross-compiler environment would? No, I'm saying that the ability to run BVT tools/processes IS a requirement for the build environment: compilation is only (an increasingly small) part of build. (I'm also only guessing at the original source's requirements, which are not mine.) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/