QT (1) Prepare the environment and. pro files

Since MeeGo uses cross-plate QT as the development environment because of Nokia, MeeGo SDK learning will also begin with QT. We have prepared two development environments, one is the MeeGo Handset simulator and the other is a local Linux (using a local environment, because the local efficiency is high, since it is only learning, it is convenient to use, finally, verify it in target ). Here we only conduct the learning and verification environment, and do not use the complete environment including rpm packaging and using QT Creator development tools.

MeeGo IA32 Handset Simulator

Using the simulator and using the MeeGo tool mad, you can simply install the simulator. For details, refer to the MeeGo handset 1.1 Development Environment Series.
. Follow these steps to create a project: app-framework-test

1. Use mad to create a QT project

$ Mad-t meego-handset-ia32-1.1 pscreate-t qt-simple app-framework-test

$ Cd app-framework-test

2. Create the Makefile file of the project based on the automatically created app-framework-test.pro file through qmake

$ Mad-t meego-handset-ia32-1.1 qmake

3. Here we compile the source code... in writing... the compilation is complete...

4. Use the cross-compilation tool chain for compilation. We can see the execution file in the build/directory.

$ Mad-t meego-handset-ia32-1.1 make

To encapsulate deb, you can use make debian-all. The deb package and source code * .tar.gz can be viewed in the directory at the previous level.

5. Verify on target. target uses a simulator.

Enable simulator:

$ Mad remote-r meego-handset-ia32-qemu-1.1.20101031.2201-sda-runtime poweron

Copy the content to the simulator. We do not use root, we use user meego, And the password is also meego.
$ Scp-P 6666 build/app-framework-test meego@127.0.0.1 :~ /Test/

Logon simulator:

$ Ssh-X meego @ localhost-p 6666, you can also replace-X with-Y

In ~ Run $./app-framework-test in the/test/directory. Then, the local X server displays the related applications. If you need to see it in the simulator, You need to first set the display environment, export DISPLAY =: 0, we can now view the original DISPALY value, in order to restore, for my environment, restore to export DISPLAY = localhost: 10.0

Local Linux (Ubuntu) Environment

It is troublesome to upload the file once for each test. Since QT is cross-platform, it is recommended to provide local environment for convenience. Install a local qt, $ sudo apt-get install libavahi-qt4-dev, create a directory local-test, and enter, create a folder src below to store source code files, we recommend that you use a build folder to store compiled files. Create a file local-test.pro so that qmake can create Makefile files based on it. Make it later. Simply copy the *. pro file automatically created by mad. If it's just a verification program, we can also write a simple local-test.pro file by ourselves, as shown below:

SOURCES = qtmain. cpp

VPATH = src

OBJECTS_DIR = build

DESTDIR = build

I removed all the above, leaving only the simplest debugging environment.

Materials

For MeeGo, its API documentation is available in http://apidocs.meego.com/1.1/core/html/index.html
But it is not easy to use. The biggest problem is that it does not have the search function. For QT, http://doc.qt.nokia.com/latest/ is available
For QT mobility, you can view in http://doc.qt.nokia.com/qtmobility-1.1.0/index.html
. A learning entry for http://doc.qt.nokia.com/latest/tutorials.html
.

Related Links: My MeeGo/Moblin articles