[Moved] Qt Creator 2.3 can’t detect ABI for embedded platform
-
I am surprised that Qt Creator 2.2.1 is failing here. It does not have the relevant code yet. Qt Creator 2.3.1 will fail.
I am currently having a patch in codereview that will open all tool chains for use whenever we fail to detect a Qt version fully, so I hope Qt Creator 2.4 will cover this use case again. Sorry for the inconvenience, we underestimated the use case quite a bit it seems:-(
-
When I run Qt Creator 2.2.1 from console it says:
Warning: Could not find ABI for '/usr/local/Trolltech/QtEmbedded-4.7.0-sh4/mkspecs/qws/linux-sh4-g++' ('Qt 4.7.0 sh4', /usr/local/Trolltech/QtEmbedded-4.7.0-sh4/bin/qmake)/sh4-linux-g++ by looking at /usr/local/Trolltech/QtEmbedded-4.7.0-sh4/lib/libQtCore.so.4.7.0:Qt Creator does not know about the system includes, nor the system defines.
So, I think 2.2.1 checks core lib for ABI too.
-
Oh, you are right of course:-( Sorry, I misremembered that.
-
The issue should be fixed in master. Please give it a try.
-
Oops!
I suppose current Qt Creator doesn't save my tool chain configuration.
Firstly, I define my custom tool chain with the ABI settings: sh-linux-generic-elf-32bit. But when I restart the program, the ABI of manually added tool chain shows: unknown-linux-generic-elf-unkonwn.Also, I can debug program on device using Debug > Start Debugging > Attach to Remote Debug Server.
But If I use Debug button (or press F5), the debugger says:
Reading debug information failed:
<executable path>: could not open as an executable file: Invalid bfd targetI think there are still some little issues with sh architecture.
-
I might have fixed that today when fixing a typo in the abi.cpp file:-)
-
I happened to notice your tool chain issue by chance here... if you do not want to rely on chance alone to get your issues fixed, then please "file bug reports":http://bugreports.qt.nokia.com/.