3.81 and windows paths

Fri Jul 28 15:46:00 GMT 2006

On Fri, Jul 28, 2006 at 11:28:42AM -0400, Igor Peshansky wrote:
> On 2006年7月28日, 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/