On 22 May 2010 06:43, Mark Brand <address@hidden>
It's also now in the attached patch for the current development
mingw-cross-env with Qt 4.6.2.
It's possible that the solution will expose new issues, so please try it
before applying! :)
Tony, are you able to confirm that this patch solves the Mac issue?
It seems to be the only thing that holds up the release.
It doesn't fix the issue, I sent a message earlier (twice since the
first had a large attachment), but it may have been blocked.
However, I just had a thought. Mark, can you check my logic.
For qt 4.6 (current dev version), this patch won't actually achieve
the desired native "bitness" of the build tools, since they are built
from unpatched sources.
This patch is not about the "endian" of the build tools. You are
right that this patch has nothing to do with the native build of the
qt tools. (You said "bitness", but it's really about byte order,
Ok, from a previous message:
> I think I've solved this. The trick was to set the architecture of the
> target platform explicitly with "-arch windows" in addition to "-xplatform"
> when invoking configure. The configure script itself also needed a change
> for this to be respected on a MAC host.
> Now automatic detection of the host platform architecture works as expected
> and the build succeeds. For the first time we have 64 bit qmake, moc, etc.
I thought the original motivation of "-arch windows" was to get native tools to match the platform. (I should stick to talking about arch or platform, then "bitness" and byte-order are implied)
It's hard to answer this completely without going into some
detail, so I offer you this for your reading pleasure
Just to avoid any misunderstanding, this is about this patch for
Qt 4.6.2 in current mingw-cross-env development:
posted earlier today, 21 May
A good start, I applied that to a clean checkout.
[...snip long explanation - thanks for that]
In conclusion, I think that this patch must be necessary for Qt
4.6.2 currently in mingw-cross-env development. Can you confirm that
it is both necessary and sufficient?
Yes, it is necessary, the build succeeds, and the test program runs. There is a slight difference in qconfig.h (defines QT_ARCH_MACOSX instead of QT_ARCH_X86_64), but this looks correct.
Thanks for taking the time to explain, you've done very well to not be confounded by the mix of Qt, Mac, and cross-compile conventions.