The correct answer to my problem is:
#include "guiddefs.h"
which I found only via much searching.
As for why the correct headers are not included, the answer to that is:
1. Typical, usual sloppy coding practices.
2. Lack of attention to detail and code organization.
3. The Windows developers
On Tue, 16 Jan 2007, Mike wrote:
[...]
> My big question is: when I add the Wine headers to my project, it seems that
> every datatype in the wine headers is undefined. I noticed that most wine
> headers don't have any #includes in them.
Normally the Wine headers have the same set of #include dire
Mike wrote:
Tried that.
But windef.h then requires tchar.h and wtypes.h.
No, it doesn't. You need to give out more details of what you're trying
to compile.
error: 'IID' does not name a type
windef.h doesn't mention IID. It's quite possible that this error is
coming from your source file
Tried that.
But windef.h then requires tchar.h and wtypes.h. I include those and
then the cascade starts. I end up having to add nearly every wine header
in the windows directory.
Once I do that then I start getting all kinds of undefined types errors
at compile time - mainly because the def
Mike wrote:
Hi.
I know this is unsupported but I am trying to use the Wine windows
headers to port some Windows code to Mac OS X. I'm not really trying
to use the Wine functionality - I use the headers more to define and
map the existing Win32 defines, and datatypes to Mac OS so that I can
m
Hi.
I know this is unsupported but I am trying to use the Wine windows
headers to port some Windows code to Mac OS X. I'm not really trying to
use the Wine functionality - I use the headers more to define and map
the existing Win32 defines, and datatypes to Mac OS so that I can make
as few ch
