From: elf AT netcom DOT com (Marc Singer)
Message-Id: <199606052055.NAA17385@netcom5.netcom.com>
Subject: Re: Windows for djgpp
To: A DOT APPLEYARD AT fs2 DOT mt DOT umist DOT ac DOT uk (A.Appleyard)
Date: Wed, 5 Jun 1996 13:55:42 -0700 (PDT)
In-Reply-To: <211A05B344F@fs2.mt.umist.ac.uk> from "A.Appleyard" at Jun 5, 96 01:34:51 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 960       
Sender: elf AT netcom DOT com

> 
>   It seems that, to write Windows applications in djgpp, I must write in the
> ordinary way, produce an A.OUT, and then translate that A.OUT to an *.EXE with
> RSX. But RSX does not have a WINDOWS.H file, and I am told to get one where I
> can. The one WINDOWS.H file that I have (it is Visual C++'s) contains these
> definitions, and often uses the words thereby defined:-
>     #define FAR               _far
>     #define NEAR              _near
>     #define PASCAL            _pascal
>     #define CDECL             _cdecl
>   So that djgpp can read this WINDOWS.H, can I simply equivalence these four
> words to null? Or edit them out wherever they occur?
> 

These macros may be very important for the Windows API to work
properly.  Generally, all of the Windows entry points require far
data and code pointers and use the pascal calling convention.  You may
have to replace PASCAL with something that GNU uses to specify that
calling convention.