Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
From:	"Tom M. Yeh" <tomyeh AT infoshock DOT com>
To:	"Cygwin" <cygwin AT sourceware DOT cygnus DOT com>
Subject:	RE: Running a NT program from cygwin
Date:	Thu, 29 Jun 2000 21:06:55 +0800
Message-ID:	<NCBBLBHKHIHIHIAOPHIIAEMKCDAA.tomyeh@infoshock.com>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2919.6600
In-Reply-To:	<200006291241.FAA05634@california.sandia.gov>

Ernest,

Thanks.

It works but it seems not a platform-independent solution. I have some GNU
makefiles that might invoke gcc or CL (VC++). And, I have to pass the top
directory into the makefiles in  subdirectories. The simplest way to use
$(shell pwd) or so. However, CL cannot interpret it correctly. It works if I
place $(cygpath -w $(shell pwd)), but I don't like the platform dependency.
I can add if/else/endif, but...   Any hint, why does the problem, I
mentioned, happen? Is it simply that Microsoft Windows doesn't know how to
interpret it (but it can interpret relative ones)?

Regards,
Tom

-----Original Message-----
From: friedman_hill ernest j [mailto:ejfried AT california DOT sandia DOT gov]
Sent: Thursday, June 29, 2000 8:41 PM
To: Tom M. Yeh
Subject: Re: Running a NT program from cygwin



Use the "cygpath" program - i.e., e `cygpath --windows /usr/local/foo`
. This will  translate cygwin paths to windows, and
vice-versa. Alternatively, when invoking a windows program, just type
the windows path.


I think Tom M. Yeh wrote:

I have a NT program, called e.exe, which is used to edit a file. When I
invoked it with a filename described by a path relative to the current
directory, it works fine. However, if I specified a path starting from the
root directory, it interprets into a wrong path. For example,

Current directory: /usr
Invoke: e include/stdio.h  -> OK
Invoke: e /usr/include/stdio.h -> FAIL, c:\cygwin\usr\usr\include\stdio.h is
searched instead of c:\cygwin\usr\include\stdio.h

In other words, it looks like no matter what path I specified, it is always
prefixed with the current directory (and discarding / if it starts with /).

Regards & Thanks,
Tom

---------------------------------------------------------
Ernest Friedman-Hill
Distributed Systems Research        Phone: (925) 294-2154
Sandia National Labs                FAX:   (925) 294-2234
Org. 8920, MS 9012                  ejfried AT ca DOT sandia DOT gov
PO Box 969                  http://herzberg.ca.sandia.gov
Livermore, CA 94550


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -