Configuring Symbian targets is cumbersome and developers are having difficulties with it. Forum Nokia has received quite a lot of queries on this subject, and even Qt for Symbian presenter at DevDays (San Francisco) found himself in trouble. Here's how to reproduce:

0) Install Qt Creator 1.3.0, Qt 4.6 for Windows and Qt 4.6 for Symbian.
1) Create a new GUI application using the wizard. Build it for windows just to ensure it works.
2) Click on "Projects" icon on the leftmost panel.
3) Under "Edit project settings for <projectname>", "Build Settings", click "Add".
4) Choose some Qt for Symbian version.
5) Click "OK" on the "New configuration name".
6) Note that two targets were added: S60 5.0 Debug and Release. Both are for the device (GCCE) instead of the emulator.

In Forum Nokia experience, most of developers will first develop their app for the emulator, then run them on the device. Therefore they will need to add yet another Build target, then change both the Debug and Release "Show details / Toolchain" to "WINSCW", so we have the 4 usual targets configured.

This is very cumbersome, so the suggestion here is either:

1) Any time the developer adds a Symbian Qt version, the tool adds 4 targets: SDK Debug, SDK Release, Device Debug, Device Release. And the "SDK Debug" should be set as default since it's what the developers will try first.

or

2) Add only the most commonly used options: SDK Debug and Device Release. In this case the default should be set to "SDK Debug". Honestly, nobody ever builds Emulator Release (UREL) targets so it shouldn't be added. Device Debug (UDEB) is very rarely built, so it can be added by advanced developers using the normal add/remove process.

Either one will better mimic the typical pattern used by Symbian developers, and already implemented in Carbide.c++ tool.

For more information please contact me at daniel.rocha@nokia.com