"Dimitrie O. Paun" <[EMAIL PROTECTED]> wrote: > Here is another problem: we are currently defining the __WINE__ symbol > to signal the headers that we are compiling Wine. This is fine. The > problem that I'm facing is that there are apps (such as wxWindows) that > want to know that they are _compiled_ (not run) under Wine. > All platforms (and Wine is a platform, even if a virtual one) define > standard symbols by default: __WIN32__, __MINGW32__, you name it.
Compiling under Wine should not IMO require defining additional symbols except probably __WIN32__. > There are valid reasons for a program to be able to test that > is being compiled under Wine, and not under MinGW for example. What are that reasons? Care to list some of them? -- Dmitry.