[RFC] Wine headers

[Dimitrie O. Paun]

Alexandre,

Patrik brought up the header location sometime ago, in this thread:
  http://www.winehq.com/hypermail/wine-devel/2002/10/index.html#540

At the time, I thought it is a bit premature, that we have other
things to do. Now I realize that this is one of those highly visible
external things, that would be a _lot_ better to fix before people
start using Winelib. Otherwise will piss people off when we change,
or we will not change because people are already using the headers.

Both versions are not good, and I think we can fix them now without
too much pain.

Here is my proposal:
  ${prefix}/include/win32  -- standard Win32 headers
  ${prefix}/include/msvcrt -- MS Visual C Runtime library
  ${prefix}/include/wine   -- Wine specific headers

It is simple (to understand & implement), clean, and pretty.
And I think it solved Patrik's problem (even if I can't quite
understand what the problem is from the first message :)),
plus a bunch of other things (like making it easy to use other
headers for the Win32 API, etc). And best of all, it seems to 
be easily implementable, no?

[Alexandre Julliard]

"Dimitrie O. Paun"  writes:
> Here is my proposal:
>   ${prefix}/include/win32  -- standard Win32 headers
>   ${prefix}/include/msvcrt -- MS Visual C Runtime library
>   ${prefix}/include/wine   -- Wine specific headers

I think everything should be under wine/ otherwise we risk conflicts
with other packages. So I'd suggest something like this:

${prefix}/include/wine/windows  -- standard Windows headers
   ${prefix}/include/wine/msvcrt   -- MS Visual C Runtime library
   ${prefix}/include/wine          -- Wine specific headers

It means the Windows headers are a bit buried instead of being
directly under wine/, but it's not too bad. As long as you don't
change anything in the source tree I could be convinced to go along
with that...