On November 29, 2002 01:43 pm, Patrik Stridvall wrote:
On 64 bit platforms we can never get 100% Win32 source compabillity
because of compiler problems. If fact we can't get 100% Win64 support
either for the same reasons so I guess Wine on 64-bit platforms will
be some kind of pseudo mode.
On December 1, 2002 11:36 am, Patrik Stridvall wrote:
So that is why we never will support 100% Win64 source
compatibillity
on 64bit platforms. We can (and presumably) will support a
LP64 variant
of Win64 but it won't be 100% source compatible.
I don't think it's nearly as bad as you
On December 1, 2002 12:35 pm, Patrik Stridvall wrote:
That solves the libc problem however compiling with -flong-int also
means that it will be impossible to call other libraries, which
means that it will be a little hard to use Unix specific library
to have extra functionallity under Unix.
On December 1, 2002 12:35 pm, Patrik Stridvall wrote:
That solves the libc problem however compiling with -flong-int also
means that it will be impossible to call other libraries, which
means that it will be a little hard to use Unix specific library
to have extra functionallity under
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
On November 29, 2002 01:03 pm, Patrik Stridvall wrote:
With your suggestion above we can, so I like it. :-)
Yay!!!
I guess the problem is that we the current setup we can not
include wine specific headers without having *our* win32 headers
in the include path. Bad.
Cool thing (me thinks) about
The only thing I don't like in my proposal is the win32 name, namely
the 32. I guess Win64 will go in the same namespace, as well as win16.
This is confusing. What about winxx or even better winapi?
Windows uses the same header files for both Win32 and Win64.
It is Win32 if _WIN32 is defined
Dimitrie O. Paun [EMAIL PROTECTED] 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
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
