On 2012-06-14 12:49, Artem Ananiev wrote:
Generation process include creating a new sizer.c file for each
structure described in "xlibtypes", compiling it and calling the
resulted binary to get offsets for all the structure fields.
How is this supposed to work when cross-compiling?
And why do you need to to this for another platform than the one we are
compiling for? (E.g., if we are generating a 64-bit macosx build, we
also do this for 32-bit macosx)
I don't remember the exact issue about Solaris-x64, why it's handled
separately and includes manual generation.
The information I was able to dig up indicated that the weirdness of how
this was compiled had caused breakage previously, and this was added as
some kind of regression test. (It was appearantly designed to catch the
error of compiling with 64-bit when 32-bit was intended, or vice versa
-- or something like that).
What are exact issues you observe with the wrapper generator?
Portability and cross-compilations issues. The main problem is: why is
it compiled for anything else than the build platform? If it is supposed
to just run on the build system, why do we need more than one? And if it
is supposed to run on the target system (!), then it will not work when
cross-compiling.
/Magnus
