From: willer@sq.com (Steve Willer)
Subject: RE: No CPP in cygwin32 for NT
22 Oct 1996 08:04:31 -0700
Sender: daemon@cygnus.com
Approved: cygnus.gnu-win32@cygnus.com
Distribution: cygnus
Message-ID: <Pine.SUN.3.91.961022082024.22847A-100000.cygnus.gnu-win32@sqrex>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sender: willer@sqrex
Original-To: Stephen Maryka <maryka@jade.ab.ca>
Original-cc: Sean McNeil <mcneils@applique.sedd.trw.com>,
        "gnu-win32@cygnus.com" <gnu-win32@cygnus.com>,
        "jbronte@doctord.com" <jbronte@doctord.com>,
        "jtaylor@station1.spherenet.com" <jtaylor@station1.spherenet.com>
In-Reply-To: <01BBB78B.B51F86E0@agte100.cadvision.com>
Original-Sender: owner-gnu-win32@cygnus.com


On Fri, 11 Oct 1996, Stephen Maryka wrote:

> I am currently trying to get the compiler working on my system and have had no luck getting it to find g++ include files such as "iostream.h".  I have tried
> including the environment variable in my environment, and have also tried the mount of /usr.  The compiler works, and finds the standard C include files but craps out on the C++ ones. 
> 
> It is unclear to me whether I should be using the Dos notation (D:\...) or the  Unix notation (//D/...) when defining the variable or setting the mount point.  I have tried several combinations with equally little success.  The only difference that I see from your examples is that my release lives on the D drive.

For C++ compilation, use CPLUS_INCLUDE_PATH, and use the Unix format. So, 
CPLUS_INCLUDE_PATH=//d/cygnus/h-i386-cygwin32/i386-cygwin32/include:/cygnus/include/g++
would probably work for you.
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
