nanogui: [patch] windef.h enhancements for VxWorks
Subject:
Re: [patch] windef.h enhancements for VxWorks
From:
Brent Thompson ####@####.####
Date:
11 Oct 2000 14:29:26 -0000
Message-Id: <39E47855.5060809@nlc.com>
Greg Haerr wrote:
> : So my solution was to use the VxWorks definitions first
> : (as I don't have *any* influence/control over #ifdef-ing
> : them to work with Microwindows). If I include the
> : <vxWorks.h> file first, then make sure to include
> : <windows.h> (which includes <windef.h>) before including
> : any ANSI header files, things work. It's a balancing
> : act, but I haven't found any easier way around these
> : type conflicts (but I am open to suggestions! :-)
>
> Do we need to include <vxWorks.h> in windows.h?
> If not, do we need any changes in windows.h or not?
Yes, my fix to this problem is still to force an include
of the VxWorks definitions before the Windows defintions.
So keep the include of <vxWorks.h> in <windef.h>.
Here is an updated #ifdef section for the include of
<vxWorks.h> in <windef.h>. I've added a few more comments
to document the specific VxWorks issues.
#ifdef VXWORKS
/* Don't include the internal Tornado header file <ntcontext.h>, **
** as the definitions in it conflict with these definitions. */
#define __INCntcontexth
/* Bring in the core VxWorks definitions as they will conflict **
** with the ones below if they are brought in later by <stdio.h> **
** or other standard ANSI header files in VxWorks. */
#include <vxWorks.h>
#endif
BAT
--
Brent A. Thompson, Next Level Communications <www.nlc.com>
1776 22nd Street #100, West Des Moines, IA 50266-1444
EMail: ####@####.#### Phone: (515)991-3853
