Is the tool chain you need to build for WinCE listed in Tools->Options->Tool chains?

Is the Qt version fully recognized in Tools->Options->Qt4? What is going wrong if it is not (very last line)? Could you please open a bug report about the issue, attaching your QtCore library for WinCE if the Qt version is not recognized?

@Tobias:

The tool chain isn’t listed. When I use Creator 2.1 the Tool chain is shown as “Windows CE” but this doesn’t appear in the list of available ones in 2.2. And I have no idea how to add it.

The Qt version is fully recognised as far as I can tell, the last line (Above helpers: None available) says “Qt version 4.7.2, using mkspec wince50domino_sbc-mipsii-msvc2005” which is what I would expect.

I’ll raise a bug report stating that WinCE isn’t included in the Tool Chain.

Steve

Are there MSVC tool chains listed?

Which ABI does the Qt version give (hover over the Qt version, please)?

MSVC is listed under the auto-detected tool chains, but it hasn’t detected any CE versions. Not sure if it should have found them.

It says arm-windows-ce-pe-unknown for the ABI.

Now raised as bug [bugreports.qt.nokia.com]

I have a similar issue with Qt Creator 2.2.1 and an arm-linux Qt build that was previously working fine with Qt Creator 2.0. I’ve manually added the Qt 4.7.2 embedded build to the Qt versions, as well as manually added the toolchain. However, there doesn’t seem to be a way to map the toolchain the the Qt version.

Edit (add more info):
In qt creator the abi of the toolchain reports as unknown-linux-generic-elf-unknown, it actually is a armv5tl-montavista-linux-gnueabi ( GCC/G++ 4.2.x )

Though there is a “toolchain” field in the project build settings, selecting the manually added toolchain path doesn’t seem to be an option.

digikata: Qt Creator examines your QtCore library and extracts an ABI from that. Any tool chain supporting that ABI is offered in the project settings to build your code with. There is no need to associate anything manually.

In the upcoming Qt Creator 2.3 (feature freeze was yesterday) you can override the ABI detected from the GCC compiler. Unfortunately that is not possible in Qt Creator 2.2.

Could you please tell me the output of your gcc’s -dumpmachine? Is that armv5tl-montavista-linux-gnueabi? Then I can make sure to detect that properly in QtC 2.3 so you do not have to meddle with the overrides:)

Yes the dumpmachine is the armv5tl-montavista-linux-gnueabi.

Just add your Qt version manually and you should be fine with that.

Tobias: Do you know if the changes for 2.3 will help with the CE problem I was having?

I do not know yet, but looking into that issue is on my todo list for 2.3.

I just hope I can get my hands on the wince tool chain for some testing:-)

If there’s anything I can do to help let me know. I should be able to clear a couple of days between now and the end of July to help if needed.

Oh, thanks! I’ll remember that:-)

Tobias Hunger wrote:

Just add your Qt version manually and you should be fine with that.

I had already added the Qt version manually, but I can’t build with that version because when build is selected, Qt creator pops up that the version has no toolchain. I’ve added the toolchain manually too, but there’s nothing allowing me to assign that manually added toolchain for that Qt version. Actually there is a field in the project build options to select a toolchain, but when a toolchain is selected, the entry comes back blank. Is there a workaround that would allow me to build?

See my 3rd comment in this thread.