Some more MSVC fixes

Dimitrie O. Paun dimi at
Wed Feb 6 10:48:42 CST 2002

On Wed, 6 Feb 2002, Patrik Stridvall wrote:

> Well. If you do as I did and just add just create 
> a Visual Studio Project (.dsp) for each DLL using the 
> MS headers is the default. I had to add "..\..\include"
> to the include path to get it to use the Wine header.

Sorry Patrik if my questions are sometimes naive, but I don't have a
Windows partition, let alone MSVC. So, here goes the question:

MSVC must have a command line version of the compiler. Wouldn't it be
easier to use our Makefile system under cygwin to compile Wine with MSVC?
> As to how good it works with MS header:
> Well, the problem is that if you don't add the path the
> Wine header files like debugtools.h doesn't
> exists so it doesn't compile very well and if
> you do the Wine headers take priority.

That's why all our private headers must reside in include/wine. That needs
to be fixed, eventually.

> Of course you could add the MS header for inclusion one
> more time after the Wine headers, but where they
> are under Windows are installation dependent and not
> very portable. :-(

Yeah, but that could be determined by configure.

> Additionally windef.h must be included first.
> #include "winbase.h"
> #include "windef.h"
> doesn't work. You have to do 

Of course. I was thinking would be nice to have a

#include "wine/prologue.h"
<whatever includes you have>
#include "wine/epilogue.h"
> #include "windef.h" 
> #include "winbase.h"
> This is a minor issue though.

Which should be fixed, I think.
> I also so got some other strange error with PCONTEXT
> in winnt.h which in didn't understand.
> In short it was a terrible mess so I primarily tested
> it with the Wine headers.

It would be sooo nice if we could compile with other headers as well. Just
compiling would be great, running the resulting executable would be

More information about the wine-devel mailing list