delorie.com/archives/browse.cgi | search |
From: | b DOT mcleod AT opengroup DOT org ("Bruce D. McLeod") |
Subject: | include paths |
28 Feb 1997 18:03:06 -0800 : | |
Approved: | cygnus DOT gnu-win32 AT cygnus DOT com |
Distribution: | cygnus |
Message-ID: | <2.2.32.19970228210226.00964208.cygnus.gnu-win32@postman.osf.org> |
Mime-Version: | 1.0 |
X-Sender: | mcleod AT postman DOT osf DOT org |
X-Mailer: | Windows Eudora Pro Version 2.2 (32) |
Original-To: | gnu-win32 AT cygnus DOT com |
Original-Cc: | damon AT osf DOT org |
Original-Sender: | owner-gnu-win32 AT cygnus DOT com |
It seems that most of the win32 stuff under bash accepts //x/ as a drive specification, except gcc include paths. bash$ ls F:/abc/def.h F:/abc/def.h bash$ ls //f/abc/def.h //f/abc/def.h bash$ cat test.c #include <def.h> main(){} bash$ gcc -IF:/abc test.c bash$ gcc -I//f/abc test.c test.c:1: def.h: No such file or directory Why do I care? I am using some build tools that do not like ':''s in the include path. Bruce - For help on using this list, send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |