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
Date: Tue, 3 Jun 2003 13:37:37 -0400
From: Christopher Faylor <cgf-rcm AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Path separator
Message-ID: <20030603173737.GC30250@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20030603170911 DOT 54952 DOT qmail AT web40611 DOT mail DOT yahoo DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030603170911.54952.qmail@web40611.mail.yahoo.com>
User-Agent: Mutt/1.4.1i

On Tue, Jun 03, 2003 at 10:09:11AM -0700, Greg Fenton wrote:
>I am looking to enhance SWISH-E ( http://www.swish-e.org )to support
>Cygwin.  It builds and runs just fine, but internally the code takes a
>configuration parameter and if it is a shell-command, converts all of
>the "/" characters to "\".
>
>
>#ifdef _WIN32
>    make_windows_path( cmd );
>#endif
>
>and make_windows_path() blindly replaces '/' for '\'.
>
>I'd like to have one binary support both Cygwin and native Win32
>environments.  Suggestions on the "cleanest" way?

You shouldn't be defining _WIN32 for cygwin.  Cygwin gcc doesn't define
this by default.
--
Please use the resources at cygwin.com rather than sending personal email.
Special for spam email harvesters: send email to aaaspam AT sourceware DOT org
and be permanently blocked from mailing lists at sources.redhat.com

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