Problems with Integration Qt for S60 and Carbide.

[ssealien]

I can't build Qt project for run on emu.
I can build only for Phone debug.
When i go to step to select available SDK i see only phone debug and phone release.
I do configure -platform win32-mwc -xplatform symbian-abld and make debug-winscw.
Where I could be mistaken

[ltomuta]

How many SDKs do you have installed? Could it be that you have configured Qt for S60 for the wrong SDK? Or else, could it be that there were errors in the configuration and you have failed to notice and fix them?

[ssealien]

I have installed UIQ3 SDK and s60v5 SDK.
But before i many install and uninstall sdk(s60v3, s60v5(0.9,1.0)).
maybe have command to uninstall Qt for s60(or it's not need? Just run config?).

[andreimarincas87]

hey, i have the same problem. have you found any solution to solve it ? i'm getting frustrated about it

[mrudulpen]

Hi,

What does devices reflect. What is the default device for your machine? Also is Qt and your sdk on same drive?

[andreimarincas87]

hey, i solve it
yes, i have everything installed on the same drive, on C:, everything in their default locations. but the problem was that i had more SDKs,

S60_SDK_3_1,
S60_3rd_Edition_SDK_Feature_Pack_2_v1_1_en and
S60_5th_Edition_SDK_v1_0_en,

and when I run "make debug-winscw", as the INSTALL file from Qt/S60 Version 4.5.0-garden says, the default sdk was 3rd Ed FP2, then i changed the default to 5th Ed, but couldn't select the 5th ed SDK's emulator (winscw) as the active build configuration in carbide, i couldn't select it in "build configuration" for a project, only for 3rd ed sdk.

Here's how i solved it : i uninstalled all other SDKs except S60 5th Edition, set is as default and followed again everything in INSTALL file from C:\qt\4.5.0-garden, and build it again. This time it created the directory C:\S60\devices\S60_5th_Edition_SDK_v1.0\epoc32\BUILD\qt\4.5.0-garden\ into the 5th ed SDK, i didn't know it works like that.

Thanks for your quick reply.

[ltomuta]

All you had to do is configure Qt again, for the new default SDK as well. But well, as long as you fixed the problem ...