X-Spam-Check-By: sourceware.org content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Why are Windows paths broken in make 3.81? Date: Thu, 27 Jul 2006 09:43:20 +0200 Message-ID: From: =?iso-8859-1?Q?J=F6rg_Schaible?= To: X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k6R7hYBf014324 Christopher Faylor wrote on Wednesday, July 26, 2006 6:26 PM: > On Wed, Jul 26, 2006 at 10:12:51AM -0600, Michael Hirsch wrote: >>> Yes. See > . >>> If you are using a POSIX-like "OS" (i.e. Cygwin), you should be >>> using POSIX paths. That's not an inconvenience, that's called >>> writing a bad makefile. If you aren't using Cygwin for the POSIX >>> environment, you should be using MinGW. >> >> I see. Unfortunately, I am trying to use cygwin to make my life >> easier on Windows, but I am still constrained to use windows >> programs. Many of them cannot use the cygwin paths, but require a >> path like "c:/my/path.exe". It will be very difficult to switch >> back and forth between path representations. I guess I do need to >> look into MinGW. > > Maybe someone here would be willing to post a sed transformation which > would change c:\some\dos\path to /cygdrive/c/some/dos/path. I already send a pointer in this thread to a mail I sent some years ago. The make functions aare still valid and makes paths transparent for make files working on Cygwin or otgher Unix environments. [snip] - Jörg -- 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/