Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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:	<20041214183915.61626.qmail@web53003.mail.yahoo.com>
Date:	Tue, 14 Dec 2004 10:39:15 -0800 (PST)
From:	Benjamin Drucker <bdrucker AT yahoo DOT com>
Reply-To:	benjamin DOT t DOT drucker AT alum DOT mit DOT edu
Subject:	problems using gcc -MM on source with Windows-style #include paths
To:	cygwin AT cygwin DOT com
MIME-Version:	1.0

I want to generate dependencies for my adopted C code
with "Windows-style" #include paths like this:

#include <stdio.h>
#include "Common\Misc\Boot.c"

I am building from a cygwin [CYGWIN_NT-5.1] window.  I
thought to use gcc -MM, but my version ["3.3.3 (cygwin
special)"] croaks on the #include paths with
backslashes.

I don't want to create an in-house tool to make
dependencies.

I am leaning against changing the C code because the
compiler we're using for actual compilation is a
Windows-only tool that needs Windows-style #include
paths.

I am looking for these kinds of solutions:
1. A version of gcc that can handle backslash include
paths.  Or a switch like "--use-dos-paths".
2. A different gnu-type tool that has been around and
is quite stable.
3. Some makefile wizardry involving sed and whatever
to do this cleanly.  This is the route I've been
pursuing and it's getting to be a mess.

cheers,
ben


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - 250MB free storage. Do more. Manage less. 
http://info.mail.yahoo.com/mail_250

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

- Raw text -