In article <[email protected]>,
Eike Ziller <[email protected]> wrote:
> So, you used the Qt 4.7.0 beta1 binary package? (Or did you build from
> source)
> Do explicitly pass an architecture to your project's CONFIG ?
> Because if you don't, your application and the debugging helpers should be
> built with the same architecture(s) (for me it is 64bit for both).
>
I have installs from both beta 1 binary and git source. Beta 1 package
come in both x86 and x86_64 and I configured source build to create x86,
x86_64, and PPC. And I verified the frameworks all have expected
architectures in them.
I tried rebuilding debugging helper libs for both installs. Both of them
resulted in x86-only dylibs.
Also, I don't think how debugging helper is build is related to the
current project.
> I wonder though, why the Qt binary package doesn't build the user's apps as
> universal binaries, it does so when building Qt from source and configuring
> it as universal.
I wonder that too. I need to add these lines in my pro file to force
Creator to build and run x86_64 when debugging:
CONFIG(debug, debug|release) {
CONFIG += x86_64
CONFIG -= x86
}
And these to have a tri-arch universal release:
CONFIG(release, debug|release) {
CONFIG += x86
CONFIG += ppc
CONFIG += x86_64
}
[rant]
A bit OT but I really don't like the choice Nokia made on including only
x86 amd x86_64 in the binary package and Creator download. The 2 target
the same CPUs, leaving the whole PPC user completely out in cold. The
choice would have made more sense on Windows release, which oddly
enough, doesn't have 64-bit binary available.
[/rant]
--
Stephen Chu
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-creator
