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 X-Injected-Via-Gmane: http://gmane.org/ To: cygwin AT cygwin DOT com From: Shankar Unni Subject: Re: posix and win32 enviornment Date: Mon, 07 Jul 2003 14:01:43 -0700 Lines: 18 Message-ID: References: <20030703011825 DOT 5597 DOT qmail AT web14202 DOT mail DOT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet AT main DOT gmane DOT org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en In-Reply-To: Igor Pechtchanski wrote: > [...] you'll be using the MinGW libraries, and your > program will not understand POSIX paths (i.e., you'll have to use Win32 > ones). Well, to be totally, utterly nitpicky, I believe "/WinNT/System32" is a valid POSIX filename which will be understood by Win32 programs as well (assuming that their current drive is "C:" :-). At the API layer, Win32 makes no distinction between "\" and "/" for filename separators (you can even open "//hostname/sharename/filename" from a Win32 program). The \-/ distinction is mainly at the command level, where most MSFT commands interpret "/" as an option prefix. But yes, you won't see your Cygwin mounts like "/usr/bin" from a MinGW (==Win32) program.. -- 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/