Mail Archives: cygwin/2004/03/26/05:13:46
Larry Hall wrote:
>
>>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.
Um, why an earth someone might run cygwin under wine? What's the catch?
If I understood correctly cygwin is meant to provide *nix things for
windows environment. (Including compilation tools, besides all others)
So why an earth windows targeted software run under cygwin? If software
is meant to be crossplatform that's an another story...
> 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? Yikes! OK, maybe I
> misunderstood what you're saying with the above but if that's
> the case, it seems to me that the bigger concern should be "will the
> software built under Wine run under Wine"? Unless you know that's the case,
> you're putting the cart before the horse. And, as I type this, I have
> the strangest feeling of deja-vu, like this is exactly the same comment
> that was made the last time this subject came up. ;-)
Well, it's pretty easy to write software that can be built under wine,
but doesn't run well or at all under wine.
Another thing is issues that might arise under real windows environment
that doesn't exists under wine (like windows file locking, permissions
and such.)
--
Jani Tiainen
"Bureaucrats! Official complaint is like trying to get drunk with root
beer."
- Wagner in Viivi & Wagner comics.
--
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/
- Raw text -