From:	jp AT nuancecom DOT com (JP Shipherd)
Subject:	More //F/ style woes
29 May 1997 21:48:38 -0700 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<3.0.32.19970529151121.00989d20.cygnus.gnu-win32@awesome.nuance.com>
Mime-Version:	1.0
X-Sender:	jp AT awesome DOT nuance DOT com
X-Mailer:	Windows Eudora Pro Version 3.0 (32)
Original-To:	gnu-win32 AT cygnus DOT com
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

Currently gcc does not allow switches like:

-I//f/include/path

It has been argued here that gcc can understand dos style paths like:

-If:/include/path

This leads to unfortunate problems when using generated dependency lists.
The colon in the path confuses gnumake.  I usually have gcc generate a
dependency file for me by using the -MM switch.  Something like:

gcc -IF:/include/path -MM test-nuance-config.c >> .Dependencies

The problem is that this puts things like F:/include/path/header.h into my
Dependency file and gnumake chokes complains:

/nuance/nuance-config/src> make
..Dependencies.win32:16: *** multiple target patterns.  Stop.

If I get rid of the drive letter colon things, gnumake works along quite
happily.

So does anyone have a solution on how to address drive/path combinations in
such a way that will work with both gcc and gnumake.  Currently I'm parsing
the .Dependencies file and replacing instances of F: with //F, but frankly
it seems like we need to find a method of naming drive/paths that work for
all the tools.

Thanks,
--jp

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -