Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Injected-Via-Gmane: http://gmane.org/
To: cygwin AT cygwin DOT com
From: Andrew DeFaria <Andrew AT DeFaria DOT com>
Subject: Re: merging mingw and cygwin
Date: Mon, 13 Oct 2003 09:03:21 -0700
Lines: 29
Message-ID: <bmeida$gnh$1@sea.gmane.org>
References: <20031011001648 DOT GG2659 AT mdssirds DOT comp DOT pge DOT com> <6 DOT 0 DOT 0 DOT 22 DOT 0 DOT 20031012123242 DOT 01d10978 AT mail DOT chariot DOT net DOT au> <20031012052757 DOT GB12191 AT mdssirds DOT comp DOT pge DOT com> <1065936902 DOT 844 DOT 19 DOT camel AT localhost> <20031012062347 DOT GA12677 AT mdssirds DOT comp DOT pge DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet AT sea DOT gmane DOT org
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en,ru
In-Reply-To: <20031012062347.GA12677@mdssirds.comp.pge.com>

Edward Peschko wrote:

>> As for needing two dev environments, you been instructed how to use 
>> cygwin to compile to both, so I must conclude you are not actually 
>> trying to comprehend the emails, just arguing for the sake of it.
>
> That is exactly my point. if cygwin can do both, and cygwin can create 
> either native win32 executables or unix executables, then WHY ARE 
> THERE TWO PROJECTS?

Have you tried to compile an application using -mno-cygwin? Have you 
tried to run the resulting executable? I have. I created an application 
using -mno-cygwin and to my surprise it became "Windows" like in that 
thinks like pathnames had to be specified in Window'ese. So before, in 
the Cygwin environment I could:

$ myapp /path/to/file

but now, after -mno-cygwin I must:

$ myapp C:\\path\\to\\file

Without Cygwin's POSIX emulation pathnames don't translate very well. 
That's probably not the only thing that you'll find as "non-unix-like" 
in the runtime environment. As such I would think producing MingW only 
versions of the various Cygwin apps would be from problematic to 
impossible, however, you are welcomed to try if you'd like to expend the 
energy...



--
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/