After a lot of googling and reading several materials, I stumbled uppon this thread discussing the same issue, but with older S60 SDK. The resolution suggests to add two new lines to .mmp file. Since I learned my lesson last time about editing .mmp in Carbide.c++ 2.0, I added these two lines into .pro file:

MMP_RULES += "OPTION CW -wchar_t on"
MMP_RULES += "MACRO _WCHAR_T_DECLARED"

Sure enough, there were no signs of those template errors after recompilation. But then a weird thing happened. Instead of template declaration compilation errors, I got warnings about duplicate declarations in mmp.

Uppon inspection I discovered that all rules I added in .pro file were there (as expected) at the end of file, but the same rules were also present in their respective sections. Somehow the inner mmp generation scheme changed and started to include rules that I missed before and needed to add through .pro file.

Hence my final step was to remove all additional lines that started with MMP_RULES from .pro file. The application is now working, but as you can see, the font and button sizes are inappropriate and the window area stretches beyond the display. I’m addressing these issuses now.

mapFile is a QString

When I installed Qt, I read the configure -help description as to what command line arguments should be used when configuring the Qt release. It said, that STL support is on by default. However in the ‘garden’ changelog, it says that for STL support, you have to use -stl switch in the configuration. I didn’t notice this contradiction the first time and trusted the configure utility output.

Further investigating this, I managed to confirm my suspicion. Qt libraries define a preprocessor flag QT_NO_STL if the STL support is not enabled – and obviously the flag is raised in my build. Seems I’ll be reconfiguring and compiling the rest of the day.

Update: Finished running configure with -stl switch and then compilation – I can confirm that the preprocessor flag is gone and I no longer get related compilation errors. I do have other issues however…

I wouldn’t dare to call it a game, since there is just one level, you are a green square and your very dumb opponents look like blue squares.

Anyway, the application loads the level layout from a text file, it keeps track of your score and live count. Your goal is to simply eat all pills and avoid contact with evil blue squares. Purple pills give you super powers for a limited time – until the effect wears off you can go berserk on the enemies.

The task of porting turned out to be more complicated than I expected. The application uses some containers and other stuff from STL, and theres the first problem – on default Carbide configuration, the use of STL is impossible:

Based on the information here I modified the .mmp file by adding the mentioned line:

SYSTEMINCLUDE    \epoc32\include\stdapis\stlport

The other suggested includes were already there. However this didn’t work, becouse on next build the .mmp file got regenerated and my change got lost. Modifying the Makefile would also not help for the same reason – it gets generated every time by qmake.

Searching for the solution actually took quite some time. At first googling discovered advices on editing the .mmp file directly, which clearly worked in previous versions of Carbide. So I plunged into the carbide project preferences, to no success eighter. Then I returned to googling again and finally found this. Its not a thread about my problem, but the last post finally solved it for me. In order to permanently add a line into the .mmp file, you have to add a declaration into the .pro file of the project in the form

MMP_RULES += "line to insert"

so in my case I had to add

MMP_RULES += "SYSTEMINCLUDE        /epoc32/include/stdapis/stlport"

Unfortunately that was not the only problem. Apparently there are some linker errors that don’t happen when compiling with MSVC 2008 and Qt 4.4 nor under Linux with gcc / Qt 4.3. I’m trying to solve that now…

As always, you can view all the sources here.

Now I could create that ui component with well known toolset of widgets:

And finally launch the emulator:

There are some setbacks. The emulator launches for quite some time, about 30-40 seconds. That doesn’t seem that much, but if you realize that it has to launch every time you decide to test-run your application, it becomes a pain quickly. Also I get compilation warnings about multiply defined symbols in symbian libraries. Thats a price for using a pre-release software, I guess.

You can find the code I used here, together with everything else that I will create on this project in my repository.

These are the tools I installed today:

• Carbide.c++ 2.0
• Symbian SDK 5th edition 1.0
• Qt for S60 4.5.0 ‘garden’

I decided to follow these step-by-step installation instructions.

So I installed Carbide C++ IDE, which in turn wanted me to install Perl runtime – and there’s a first problem. Apparently the recommended Active Perl version (5.6.1.635) installer has problems when run under Windows Vista – it ends with internal error 2739.

Running th... again didn't fix the problem.

This turned out to be a general installer issue, and as explained here, it affects other programs too. The first solution I found – for Adobe products installation – helped with Active Perl as well. Great. I only had to add a path to the perl executables to PATH after that manually, no big deal.

Next we have the Symbian SDK 5th edition v1.0. One has to be careful to select a generic SDK, not the default N97 SDK for download. Frankly I’m not certain what the differences are, but I don’t have any N97s around, so thats why. The package took a while to download (600-ish megs) and a lot longer to install. It also included a CSL Arm Toolchain. The process, although a little long, went smooth.

The main beast of course was the Qt itself. I chose to use the ‘garden’ release of mobile 4.5-based Qt, as its the newest at the moment. There are a couple things to do before you let the machine crunch for the rest of the day – and its all written here.

The installation instructions cover all needed info for the compilation, so all you really need is to follow them and have a lot of time on your hands. The configuration took about an hour on my laptop with 2.1GHz CPU. The compilation itself took twice that long. Thats incomparably shorter to normal Qt release compilation. The reason is that the ‘garden’ contains only some of Qt’s libraries:

• QtCore
• QtGui
• QtNetwork
• QtScript
• QtSvg
• QtXml
• QtTest

And some are still incomplete, for the detailed info look at the changelog.

Thats it, the Qt is ready, SDK installed and Carbide is ready and running. Time for that Hello World! again.

I’m just beginnig my practical training here at ICT of Jyväskylä University of Applied Sciences in Finland – and the hot topic here is the anticipated release of Qt on S60. Seems I’ll be developing example applications on this platform for a while. I did some apps in Qt before, but as I don’t have any mentionable experience with mobile programming, there are a lot of questions in my head. Here I would like to sum up my experience with this environment and present the answers as I discover them.

I hope somebody will find this useful.