Hi,
According to what I found on the web are resources always little-endian
because MS does not support/wrote OSes for big-endian processors. There
are a couple of questions that go with this:
- Is it true that MS only has little-endian version?
- Should I support big-endian at all in wrc? Currently, wrc generates
the native endianness of the platform, but it does _not_ convert binary
resources (such as bitmaps). It is actually extremely difficult to mix
endianness in resources because everything has to be examined and
_cannot_ be guaranteed to be correct (such as RCDATA).
- Should wine only use little-endian in the resources? In my oppinion,
yes. Let the resources be the same all the time and let the
resource-loader take care of conversion. There is a comment in a header
about byte-swapping and wrc. I really would prefer to have byte-swapping
in wine rather than wrc. Mainly because wine already requires to do the
analysis of resource-contents, whereas wrc only packs data (without
contextual/semantical knowledge).
- Who has tried to run wine(lib) on big-endian processors and what are
the experiences?
Greetings Bertho
