Re: Mingw32 header - commdlg.h

[Mumit Khan <khan@xraylith.wisc.EDU>]

"dale henderson" <dalekh@hotmail.com> writes:
> I am having a problem compiling wxWindows using this header. What does
> this mean?
> 
> In file included from dc.cpp:50:
> C:\\MINGW32\\BIN\\..\\lib\\gcc-lib\\i386-mingw32\\egcs-2.91.66\\..\\..\
> \..\\..\\i386-mingw32\\include\\commdlg.h:197: `APIENTRY' was not
> declared in this scope
> C:\\MINGW32\\BIN\\..\\lib\\gcc-lib\\i386-mingw32\\egcs-2.91.66\\..\\..\
> \..\\..\\i386-mingw32\\include\\commdlg.h:197: `__CDHOOKPROC' was not
> declared in this scope
> C:\\MINGW32\\BIN\\..\\lib\\gcc-lib\\i386-mingw32\\egcs-2.91.66\\..\\..\
> \..\\..\\i386-mingw32\\include\\commdlg.h:197: `HWND' was not declared
> in this scope

[ and so on ]

I hope you realize that the type of information you've provided is pretty
much useless for diagnostics. The only way to know what's going is to 
either (1) look at the entire sources, or (2) look at the preprocessed 
sources (-save-temps option to gcc will create one).

Also, you don't say if you're using stock egcs-1.1.2 or if you've modified 
the headers (the commdlg.h included in my egcs-1.1.2 distribution didn't
have 197 lines!).

It could simply mean that the code that included commdlg.h didn't include
windows.h first, and hence missing all the win32 api specific typedefs
and macros (such as APIENTRY, HWND, etc); or, it could be something 
entirely different.

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com