Following Marcus Meissner's advice how to build a WoW64 setup (thanks!),
I have succeeded in building a set of co-installable i386/amd64 Debian
packages. Those won't make it into the "wheezy" release as I was just a
bit late for the freeze, but I have uploaded packages to experimental.
What didn't
Hi,
after the effort on the Debian wine packages has progressed to a point
where it's likely that we'll release wheezy with a stable wine version
that is not completely out of date, I'd like to take things a step
further.
I recently spent some time looking at ways how we could build Debian
packag
* Alexandre Julliard:
>> Please have a look at the revised patch I just posted. I have avoided
>> possible conflicts by only defining the macros if they are needed.
>
> A different name is much better.
Alright. Any suggestions?
-Hilko
* Alexandre Julliard:
>> Is this form okay?
> You should pick different names to avoid possible conflicts.
Please have a look at the revised patch I just posted. I have avoided
possible conflicts by only defining the macros if they are needed.
-Hilko
* Alexandre Julliard:
> Hilko Bengen writes:
>
>> So, do I need to define my own htobe16 and htobe32 functions or macros
>> based on whether WORDS_BIGENDIAN is defined or not?
>
> Yes.
I have tested these macros on Linux/PowerPC and they still produce the
same results a
* Alexandre Julliard:
> endian.h is not portable, you should use the endianness defines from
> the Wine headers instead.
So, do I need to define my own htobe16 and htobe32 functions or macros
based on whether WORDS_BIGENDIAN is defined or not?
-Hilko
