Yes, it can be good but it will be better if arm or mips(el) g++ cross compilers treated as custom embedded device? Maybe a board icon or something else suits well i think.
As i see current code checks exactly "g++" not contains "g++" so Qt Creator claims my Qt installations as invalid. I'm creating a bug report for this issue. On Wed, Apr 7, 2010 at 15:52, Daniel Teske <[email protected]> wrote: > On Wednesday 07 April 2010 14:28:26 Teske Daniel (Nokia-D-Qt/Berlin) wrote: > > On Wednesday 07 April 2010 12:15:52 ext Berk Demirkır wrote: > > > Hi, > > > > > > I'm currently using lastest snapshot of Qt Creator. For some reason it > > > doesn't recognize my arm-linux-g++ toolchain based Qt installation. I > > > was investigated source code a bit and realized that > > > QtVersion::updateToolChainAndMkspec() function doesn't handle my > > > toolchain. > > > > > > Since Qt 4.7.0 TP released i can not work with new Qt Creator. Also > note > > > that my mips based Qt installation doesn't handle by Qt Creator. I > think > > > this problem affects all custom embedded toolchains. > > > > > > Please correct me if i'm wrong. > > > > No, you are probably right, could you create a bug report for that? > > > > We probably will treat those embedded toolchains as beeing for the > desktop > > target, even if that's somewhat confusing for the user. > > > Ah was a one line fix. (Or at least I hope so.) All mkspecs where QMAKE_CXX > ends with g++ are now treated as desktop g++. That's almost how we did that > in > 1.3. > > daniel > > _______________________________________________ > Qt-creator mailing list > [email protected] > http://lists.trolltech.com/mailman/listinfo/qt-creator >
_______________________________________________ Qt-creator mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-creator
