This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
Re: runtime header structure
- To: cygwin at sourceware dot cygnus dot com
- Subject: Re: runtime header structure
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Tue, 1 Aug 2000 20:46:02 -0400
- References: <3986F8DA.11182.C44B33@localhost>
- Reply-To: cygwin at sources dot redhat dot com
On Tue, Aug 01, 2000 at 04:20:42PM -0800, Paul Garceau wrote:
>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".
/usr/i686-pc-cygwin/... is obsolete. The "old" version of setup
used to delete this directory if it could, but this code is currently
missing from DJ's version of setup.exe.
> 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?
/usr/local/include would be the preferred place to put new headers.
You shouldn't be polluting the "standard" locations with your changes.
cgf
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com