Kevin wrote:
Binary compatibility with win64 will be just about impossible as the long datatype is used extensively throughout the headers and code
doing -Dlong=int works in simple cases, but not as a general rule
Can you give an example of a non-simple case?
What about defining LONG as int in win64?
--Juan
____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
On Tuesday 19 July 2005 4:31 pm, Juan Lang wrote:
Can you give an example of a non-simple case?
What about defining LONG as int in win64?
you could start with running "grep long *" inside the include directory. Every instance would need to be changed in some form, I count well over a thousand instances in just the headers.
"Kevin Koltzau" kevin@plop.org wrote:
you could start with running "grep long *" inside the include directory. Every instance would need to be changed in some form, I count well over a thousand instances in just the headers.
We need to replace 'long' by 'LONG' and 'int' by 'INT' in the headers. That's a job for a simple script. Then synchronize headers with an actual implementation, that's a little bit harder since we need to closely inspect every API implementation.
On Wednesday 20 July 2005 05:30, Dmitry Timoshkov wrote:
"Kevin Koltzau" kevin@plop.org wrote:
you could start with running "grep long *" inside the include directory. Every instance would need to be changed in some form, I count well over a thousand instances in just the headers.
We need to replace 'long' by 'LONG' and 'int' by 'INT' in the headers. That's a job for a simple script. Then synchronize headers with an actual implementation, that's a little bit harder since we need to closely inspect every API implementation.
and what about .spec files and winebuild ?
Regards, Raphael
-
Dmitry Timoshkov -
Juan Lang -
Kevin Koltzau -
Raphael