Using Wine headers on Mac OS X
lists at michael-amorose.com
Tue Jan 16 14:55:16 CST 2007
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 default wine/windows headers don't
seem to include other #includes in them that define the types each file
relies on. For example:
error: 'IID' does not name a type
extern const IID GUID_NULL;
There are *no* #includes in cguid.h so it appears IID is not being
defined for that file unless some other header that defines it is pulled
I hope there is one simple include file I can include to solve this
problem and not have to spend a day going through the entire
wine/windows file set and including everything.
Robert Shearman wrote:
> Mike wrote:
>> 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 changes to the Windows code I am porting as possible.
>> 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.
>> is there some precompiled or metaheader that I should be including in
>> all of the wine files in order to get the compiler to see the data
> I'm not quite sure which data types you mean, but it sounds as though
> the only header file you want to include is windef.h.
More information about the wine-devel