[Solved] Qt for Symbian 4.7.1 - choosing multiple S60 folders



  • I installed Qt for Symbian 4.7.1 with just one SDK folder S^3 specified.
    Now how can I specify more than one SDK folders? Up to 6 folders are supported by installer.

    Should I uninstall the previous one and redo the whole thing or any short cut to do this?



  • I usually reinstall it back.



  • ya that's what I eventually did, but would prefer some easier way to just set this up :)



  • Hi,

    did the Qt 4.7.1 worked with no problem with S^3? Are u using the Carbide.C++? I (and not only me) face some very strange behavior. I tried to describe it here: http://developer.qt.nokia.com/forums/viewthread/2175
    Thanks for looking.
    BR
    STeN



  • Hi stenlik,
    Didn't use Carbide.c++. Me and a few team members ran into few issues while trying mobility on Qt 4.7.1 on S^3, so put it on hold. Got lots of other things going on. So at present I'm waiting for the next stable version of Qt Nokia SDK, I'm sure many of these critical issues will be resolved by then.



  • Hi chetankjain,

    Thanks a lot for your reply, I am using Carbide.C++ because I mix Symbian C++ with Qt...

    I have 2 questions I would like to ask you:

    1/ From your answer I suppose you are using the Qt Creator. Does it mean that with Qt Creator I can create and deploy pure Qt application on Symbian^3 with Qt 4.7.1 with no problem?

    2/ Assuming that I built my Qt code under Carbide.C++ with older S60 5th SDK which already supports Qt 4.7.1, then I think - unless I do not need any specific Symbian^3^ C++ functionality, or the Qt is not based on some Symbian^3^ specific functionality, I can use the build also on Symbian^3^ devices and it will behave exactly in a same way as if built with Symbian^3^ SDK. Is that right?

    Thanks for your replies.

    Regards,
    STeN



  • stenlik, there are some known limitations about building and deploying from creator, but yes it is possible. But not sure about 4.7.1 (I've tried 4.7.0).
    About second question. In general answer is yes. But some small problems always can occur.



  • hi stenlik,

    i'm just dipping my hands with qt mobility api, so treat me as a rookie there :)

    I am using Carbide.C++ because I mix Symbian C++ with Qt
    I think you can also start looking at Qt Nokia SDK and using Qt creator .. from what I inferred from the press releases earlier, that will be the way to go for future Qt developers - unified platform

    1. majorly yes, but i ran into issues with some mobility examples and creator was not the cause here. you can check out the full nokia sdk - very helpful IMO

    2. i do not really qualify to answer this as no prior experience on carbide c++. but i did compille some examples using creator and s60 v5.0 SDK and i did manage to run them on a N8 (symbian^3) here. again ran into issues when I tried mobility stuff


  • Moderators

    stenlik: Are you aware that Qt Creator does support C++? You can mix Symbian and Qt in your project, no problem there.

    To 1) It depends on what you mean with "deploy". Qt Creator fully supports development on Symbian, so you can build your project and run/debug it on a Symbian device. This of course includes deploying it to the device.

    What Creator does not yet support is publishing of your application. So if you refer to "putting an application on lots of devices" then we do not yet support deployment. The terms seem to get mixed a lot, that is why I explicitly mention this.

    To 2) That should work. In the real world I would develop on a symbian 5th edition when possible, just to make sure no Symbian 3 APIs sneak into the code:-) Of course you are save as long as you stay in Qt/Qt mobility land:-)



  • so tobias from your reply, I infer that in the future creator will directly publish my app to ovi ? is that in your roadmap? it would be amazing I'd say :)


  • Moderators

    chetankjain: We are always trying to make Creator rock:-)



  • [quote author="chetankjain" date="1289530500"]I installed Qt for Symbian 4.7.1 with just one SDK folder S^3 specified.
    Now how can I specify more than one SDK folders? Up to 6 folders are supported by installer.

    Should I uninstall the previous one and redo the whole thing or any short cut to do this?[/quote]

    Those additional folders are there to copy Qt src and IIRC they were originally put there to support installing to multiple SDKs and possibly to SDKs that didn't get registered to Windows registry. So your install it to one SDK multiple times won't help as there is only one output dir in Symbian SDK (no shadow builds).



  • hi koshui, this was the scenario:

    I installed Qt for Symbian 4.7.1 and specified it to point to Symbian^3^ SDK folder. After installation, I then downloaded and installed S60 v5.0 SDK and also S60 v3.x SDK (for trying Qt on my E90) ... now the problem I saw was that only the Symbian^3 SDk was being shown in my creator under Options->Qt4->Symbian SDK tab ... so how to get the latter 2 symbian SDKs registered?

    I ended up reinstalling the whole thing again


  • Moderators

    chetankjain: You can manually register SDKs in Creator. Just go to Tools->Options->Qt versions and add a new one. You need to pick the qmake of the Qt version and set a lot of stuff for symbian (SDK root (the directory containing epoc32), pathes to your GCCE, etc. but it is doable. You can have an arbitrary number of Symbian SDKs registered with Qt Creator and switch between them as needed.

    tamhanna: How does the Qt Simulator play into this? It is completely independent of anything you do with your Symbian SDK setup. Or are you referring to the symbian emulator? That should depend on the EPOCROOT you set (and what you put there).



  • ah tobias, i truly missed this step, i've added Qt sdk paths here in the past, but never noticed that I could add s60 sdks too :o ... i was hunting for it in the s60 tab, the additional s60 sdk related fields show up only after you pick the qmake.exe under the s60 sdk and I never tried this far. whereas they show up on selecting an existing s60 sdk option.

    yes this means I can have 'n' number of sdks in theory

    thanks :)



  • [quote author="tamhanna" date="1291577672"]Keep one thing in mind: for the Qt, there can be only one.
    The reason: Qt writes support libraries into the SDK on install. So whichever Qt you install last, is the Qt you will have the pleasure of using in the simulator.
    [/quote]

    [quote author="tamhanna" date="1291579341"]Tobias, sorry, I meant the SDK. Not the Qt Simulator, please forgive...[/quote]

    I have 6 "Qt for xxxxxxxx" SDKs, 3 "S60/Symbian" SDKs, 2 Simluators and 1 remote compiler in my settings right now and don't see any issue!



  • [quote author="tamhanna" date="1291580226"]

    Caveat Emptor!

    I have mver heard of this configuration being used productively anywhere. So expect all kinds of quarrels between the instances.

    And keep us posted how it goes!
    [/quote]

    well you heard it here the first time! maybe i want to test my Qt app on multiple Nokia devices, i'm becoming famous for my personal library of devices and why would they quarrel? have you seen how creator handles all these various environments and configurations? can you give me a reproducible step that could cause a conflict



  • [quote author="chetankjain" date="1291569756"]so tobias from your reply, I infer that in the future creator will directly publish my app to ovi ? is that in your roadmap? it would be amazing I'd say :)[/quote]
    I assume you mean once a content item is already set up with metadata. Just to upload to a defined ovi content item.

    tam: I'm pretty sure they are in different directories. They won't conflict. Works here. That is, multiple SDKs.



  • Hi Tobias,

    [quote author="Tobias Hunger" date="1291569554"]stenlik: Are you aware that Qt Creator does support C++? You can mix Symbian and Qt in your project, no problem there.

    To 1) It depends on what you mean with "deploy". Qt Creator fully supports development on Symbian, so you can build your project and run/debug it on a Symbian device. This of course includes deploying it to the device.

    What Creator does not yet support is publishing of your application. So if you refer to "putting an application on lots of devices" then we do not yet support deployment. The terms seem to get mixed a lot, that is why I explicitly mention this.

    To 2) That should work. In the real world I would develop on a symbian 5th edition when possible, just to make sure no Symbian 3 APIs sneak into the code:-) Of course you are save as long as you stay in Qt/Qt mobility land:-)[/quote]

    Let it make more clear to me:

    1/ I need to use Symbian C++, because I develop for Symbian a long time (7yrs), so I am really familiar with it and I have already a lot of sources and Qt does not have (yet?:) API I am using. But where I can use Qt (especially UI now) I will use it.

    2/ I would like to use Qt Creator instead of the Carbide.C++, but the problem (as far as i test it) is that I can use it only for device builds, so I cannot test on standard Symbian emulator - is that right? in some projects I have .exe daemons running 50.000 lines of code and I need only front-end for them, which I can do in Qt Creator, but again I cannot test on emulator...

    And of course -there will be still Symbian C++ only projects for some industry solutions deeply integrated in OS I need Carbide.C++ still.

    Thanks for your comments.

    STeN

    BTW - Qt community is great!!!



  • Well there is a Symbian Simulator (rather than emulator) in QtCreator. I'm not sure how well it works with your Symbian C++ projects though (I've mostly used pure Qt on there). The SDK integrates well in to QtCreator so it technically should work. I don't think you'll need Carbide (what does it offer that you need currently?).

    Remember that ForumNokia has RDA devices (a heap of Nokia phones) that you can test your app on remotely.

    Qt has a lot of the back-end APIs too (not just UI). Although, if there's something deep in Symbian you want, you can always rely on Symbian C++.



  • Hi xsacha,

    Thanks for the reply - I will test it and come back with more concrete questions. In fact I did not tried the Symbian Simulator in Qt Creator. From some reason (stupidity;) I thought it is for pure Qt applicaitions only, but if I can mix Qt and Symbian C++ I will probably prefer it over Carbide.C++. From the same reason I also thought that Qt Creator cannot mix Qt and Symbian C++...

    On the other side Carbide.C++ is not a bad tool and it is always good to have options to choose especially if you are already familiar with the IDE and its tricks.

    Might be having some info page about both IDEs on this web pages describing migration from Symbian to Qt and various possibilities/advantages/drawbacks is not a bad idea...

    BR
    STeN


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.