December 7, 2009 at 16:28Qt development for Symbian S60 officially available
Waited a long time for the official release of Qt 4.6.0, since the Trolls promised to officially support the development of S60 on Qt. While there was a Developer Preview - the developer could write applications for the S60, but there were no mechanisms for delivering applications to the end user (i.e. the user).
At the time of release 4.6.0, they promised to fix this situation, and in forums and in correspondence, trolls answered questions regarding “deploy” in (I really do not like the Russian analogue of this word: “deployment”) applications on devices like this: “Before this release is not, wait for the official release. Everything will be there! ”
What has changed with the release of the official release?
Well, wait. After its release, as far as possible I tried to figure out what had changed.
I went into the documentation and got acquainted with the officially proposed mechanism:
“Deploy” applications for Symbian.
I summarize:
1. Static linking is not supported at all (but at this stage it would be useful).
2. Together with your application, you need to pull the Qt libraries (I'll tell you later what this is connected with).
3. Together with the application, you need to pull Open C / Open C ++ libraries version 1.6.
The mechanism is relatively automated.
Why is it necessary to pull the Qt library with your application? There are two reasons for this:
1. So far they have not made the mechanism for installing dependencies through the Ovi-store. So that when installing the first Qt, applications are installed automatically by agreement of the user of the new version of Qt library and Open C / Open C ++. But now they are working on it and promise to do it and integrate it into the Ovi-store in the first quarter of the 10th year, with the release of 4.6.1 version of Qt libraries.
2. Most importantly, Qt 4.6.0 for S60 will not be binary compatible with future versions. Binary compatibility with future versions will begin only with Qt 4.6.1. That is, if you compile the application and publish it, and suppose that the normal mechanism for installing Qt libraries as dependencies already exists, then the application will need to be reassembled with new libraries, and the user, along with the installation of the new version of Qt libraries, should update all old applications. That's precisely for this reason there is no mechanism for installing Qt as a dependency (when the next Qt release is released, all Qt applications based on the previous release will stop working).
In fact, it turns out that this is again a pre-release for developers not particularly different from previous release candidates.
But these are sad moments. Now about the joyful. Allesandro (one of the trolls who is responsible for public relations regarding the development of Qt for Symbian) published video tutorials on deploying the environment for development under Symbian:
1. You need to download and install all components: ovisute , carbidecpp , activeperl , s60sdk , openc , apptrk .
Setting the environment:
2. How to install Qt for Symbian on the phone and on the desktop. And how to configure QtCreator.
3. How to write an application and install it on the phone and debug it directly on the device in QtCreator, without using slow Eclips.
Well, everything is quite simple. You can start trying to write.
PS: I really look forward to the release of this SDK for Linux. I know that there are already folk crafts, but I want a fully functional version without additional tambourines. Who cares about the Linux version, useful information can be found here:
http://labs.qt.nokia.com/blogs/2009/10/28/a-new-symbian-toolchain-for-linux/
http: / /lizardo.wordpress.com/
http://martin.st/symbian/
At the time of release 4.6.0, they promised to fix this situation, and in forums and in correspondence, trolls answered questions regarding “deploy” in (I really do not like the Russian analogue of this word: “deployment”) applications on devices like this: “Before this release is not, wait for the official release. Everything will be there! ”
What has changed with the release of the official release?
Well, wait. After its release, as far as possible I tried to figure out what had changed.
I went into the documentation and got acquainted with the officially proposed mechanism:
“Deploy” applications for Symbian.
I summarize:
1. Static linking is not supported at all (but at this stage it would be useful).
2. Together with your application, you need to pull the Qt libraries (I'll tell you later what this is connected with).
3. Together with the application, you need to pull Open C / Open C ++ libraries version 1.6.
The mechanism is relatively automated.
Why is it necessary to pull the Qt library with your application? There are two reasons for this:
1. So far they have not made the mechanism for installing dependencies through the Ovi-store. So that when installing the first Qt, applications are installed automatically by agreement of the user of the new version of Qt library and Open C / Open C ++. But now they are working on it and promise to do it and integrate it into the Ovi-store in the first quarter of the 10th year, with the release of 4.6.1 version of Qt libraries.
2. Most importantly, Qt 4.6.0 for S60 will not be binary compatible with future versions. Binary compatibility with future versions will begin only with Qt 4.6.1. That is, if you compile the application and publish it, and suppose that the normal mechanism for installing Qt libraries as dependencies already exists, then the application will need to be reassembled with new libraries, and the user, along with the installation of the new version of Qt libraries, should update all old applications. That's precisely for this reason there is no mechanism for installing Qt as a dependency (when the next Qt release is released, all Qt applications based on the previous release will stop working).
In fact, it turns out that this is again a pre-release for developers not particularly different from previous release candidates.
But these are sad moments. Now about the joyful. Allesandro (one of the trolls who is responsible for public relations regarding the development of Qt for Symbian) published video tutorials on deploying the environment for development under Symbian:
1. You need to download and install all components: ovisute , carbidecpp , activeperl , s60sdk , openc , apptrk .
Setting the environment:
2. How to install Qt for Symbian on the phone and on the desktop. And how to configure QtCreator.
3. How to write an application and install it on the phone and debug it directly on the device in QtCreator, without using slow Eclips.
Well, everything is quite simple. You can start trying to write.
PS: I really look forward to the release of this SDK for Linux. I know that there are already folk crafts, but I want a fully functional version without additional tambourines. Who cares about the Linux version, useful information can be found here:
http://labs.qt.nokia.com/blogs/2009/10/28/a-new-symbian-toolchain-for-linux/
http: / /lizardo.wordpress.com/
http://martin.st/symbian/