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 Message-ID: <03fc01c2725d$27a7ab60$4c9d31d2@c03007967a> From: "Travis Howell" To: References: <4 DOT 3 DOT 1 DOT 2 DOT 20011227110206 DOT 023a7378 AT pop DOT ma DOT ultranet DOT com> Subject: Re: windres doesn't accept DOS paths Date: Sun, 13 Oct 2002 12:06:33 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 I was just wondering, are there any plans to fix the problem of Cygwin's windres failing to understand windows style paths which is mentioned below ? Larry Hall (RFK Partners, Inc) wrote: > At 10:00 AM 12/27/2001, Matthew Brett wrote: >> Hi, >> >> I think someone mentioned that if cygwin utilities do not accept DOS >> paths then this should be considered a bug. Just to report then, if >> you pass a DOS path to windres, it barfs: >> >> windres "c:\test.rc" >> >> gives >> >> gcc: c:test.rc: No such file or directory >> gcc: Warning: `-x c-header' after last input file has no effect >> gcc: No input files >> windres: warning: preprocessor failed >> windres: no resources > > There does appear to be some issue here. Even at the DOS prompt, the > backslash needs to be escaped in order to work (in the example above). > Other Cygwin utilities don't have this problem. It's worth noting > that the POSIX path and the "c:/test.rc" alternative paths both work > fine though with windres. > > > > > Larry Hall lhall AT rfk DOT com > RFK Partners, Inc. http://www.rfk.com > 838 Washington Street (508) 893-9779 - RFK Office > Holliston, MA 01746 (508) 893-9889 - FAX -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/