> Well i the changes i briefly outlined before would probably solve this > problem: by giving the spec argument for "Desktop" builds and leaving it away > for "Cross" builds.
Having a separate Cross building target instead of lumping everything together into "Desktop" is here: https://bugreports.qt.nokia.com/browse/QTCREATORBUG-3290 > My plan is to make the "Desktop" stuff switch to cross mode if the arch > is different from the build platform. ... which does not work when e.g. developing on Linux for x86-based embedded Linux devices. We can do special-cases for Meego, but there are lots of others out there and we can not do special cases for all of them. With Intel pushing their atoms into the embedded space we will most likely see more and more of those, too. > Given the fact that you normally don't > switch toolchains on cross development, and if you do you also use normally > a qt build with the other toolchain, disabling toolchain switching for > "Cross" builds would fix all these problems? I am tempted to just make the mkspec the tool chain suggests configurable and/or add a "this is for cross-compiling" flag to the Qt versions. These changes will make the decission which tool chain will work with the Qt version more error-prone though. In short: I have not yet thought of a solution that does not break other of the less common use-cases while fixing yours. Suggestions (and patches) are -- of course -- welcome. Best Regards, Tobias Tobias Hunger Software Engineer Nokia, Qt Development Frameworks Nokia gate5 GmbH Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B Umsatzsteueridentifikationsnummer: DE 812 845 193 Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori _______________________________________________ Qt-creator mailing list Qt-creator@qt.nokia.com http://lists.qt.nokia.com/mailman/listinfo/qt-creator
