X-Spam-Check-By: sourceware.org
Date: Fri, 28 Jul 2006 11:40:50 -0400
From: Bob Rossi <bob_rossi@cox.net>
To: cygwin@cygwin.com
Subject: Re: 3.81 and windows paths
Message-ID: <20060728154050.GB4533@brasko.net>
Mail-Followup-To: cygwin@cygwin.com
References: <44C92033.A2978A8E@dessent.net> <17609.11132.462789.443104@lemming.engeast.baynetworks.com> <20060727221136.GD6653@trixie.casa.cgf.cx> <17610.6020.12729.506044@lemming.engeast.baynetworks.com> <17610.7126.60597.468701@segfault.lan> <17610.8103.778129.918123@lemming.engeast.baynetworks.com> <44CA2188.9050905@equate.dyndns.org> <20060728144330.GA4533@brasko.net> <20060728145443.GE16728@trixie.casa.cgf.cx> <Pine.GSO.4.63.0607281126420.9201@access1.cims.nyu.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.63.0607281126420.9201@access1.cims.nyu.edu>
User-Agent: Mutt/1.5.11
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Fri, Jul 28, 2006 at 11:28:42AM -0400, Igor Peshansky wrote:
> On Fri, 28 Jul 2006, Christopher Faylor wrote:
> 
> > On Fri, Jul 28, 2006 at 10:43:30AM -0400, Bob Rossi wrote:
> > >> Well, the whole point of cygwin is to give a POSIX-compatible
> > >> environment in win32. So it's aiming to be like linux, not windows.
> > >> This means that if something like a makefile parses fine in linux, but
> > >> not in cygwin (barring linker stuff), something is wrong.
> > >
> > >Yeah, what's wrong is that cl doesn't accept posix paths. For some
> > >reason, they were added, we all got addicted to it, and now it's being
> > >ripped out from underneath us. It's not a very friendly thing to do.
> 
> If you are invoking cl in your Makefiles, they are no longer POSIX or
> Linux Makefiles, and you might as well run your paths through cygpath
> before sending them to cl.

Yes, this is the solution I came up with, but it's not an easy task.
It's also slightly ugly, since we compile with g++/gcc on other systems.

> > <profanity deleted>
> 
> Hmm, I thought we didn't have an automatic censorship filter on this list.
> I guess you just have to be *really* annoyed to trip it.
> 
> OTOH, a simple "here we <expletive> go again" would probably have
> sufficed...

At least I understand this.

Thanks,
Bob Rossi

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