Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: "Paul Garceau" Organization: New Dawn Productions To: cygwin AT sourceware DOT cygnus DOT com Date: Tue, 1 Aug 2000 16:20:42 -0800 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: runtime header structure Reply-to: Paul Garceau Message-ID: <3986F8DA.11182.C44B33@localhost> X-mailer: Pegasus Mail for Win32 (v3.12c) Hi folks, Please, forgive the newbie nature of this question. I am in the process of porting a rendering engine for Cygwin. Primarily, the purpose is to allow multiple development environment support for the rendering engine in question (CrystalSpace). Currently I am working on porting a Cygwin version of a DirectX 3 (NT4) version of CrystalSpace. In reviewing the header structure (/usr), I couldn't help but notice that there were apparently duplicate headers involved. On the one level, I see "usr/i686-pc-cygwin/include" and I also see "usr/include". Is there any subtle difference between these two sets of headers or are they simply symlinked? If the latter (symlinked), then which is the "include" directory which has the symlink, or are they both symlinked from somewhere else (gcc-lib?)? I am trying to ascertain which "include" directory is the actual default "include" directory, and which is not. Finally, which is the "include" directory which is assumed when g++ is active? Since I am attempting to integrate a new, NT4 based API, which of the directories (usr/include, usr/i686-pc-cygwin/include, or other) is the recommended location for new headers? Thanks for your patience and your replies. Peace, Paul G. Nothing real can be threatened. Nothing unreal exists. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com