Meego handset 1.1 Development Environment [5]: A desktop application

In implementing Hello World on MeeGo handset 1.1 SDK, we further discuss how to use the ssh client to interact with the hanset runtime simulator:

1. Use QT Creator as the development environment and run on the simulator (target.
2. How to run on a local window through the SSH command line (host performance is much better than simulator)
3. How to use the set Environment Parameter display to run the app on the simulator through the SSH command line

In addition, we want to place an icon on the target (simulator. On the simulator, click the triangle symbol in the middle of the toolbar to display the following interface:

Here we can see the application of SMS. View the/usr/share/application directory and find that there are multiple application desktop files, while sms is only one of them. Related Icon files can be found in/usr/share/icons/hicolor. Therefore, if only one sms application is displayed, It is abnormal. Therefore, I performed the following operations to restore the/usr/share/application/sms. desktop file ~ /, And then start the file from ~ . In this way, sms will be arranged as the last application, not the first one. The specific cause is unknown, but the display of the simulator's app icon can be corrected. After modification, the page is shown in the right figure below.

After the environment is designed, We will load the hello world Program as an icon. The following is a reference:

 

• Http://wiki.meego.com/Packaging/Guidelines
• Moblin: Kernel compilation and RPM packaging (2): rpm Packaging

Step 1: Use the mad tool to create an initial Environment

When installing Meego SDK on wiki, terraplatform
Complie toolchain: Creates the target development environment. As follows:

Mad-T meego-handset-ia32-1.1 pscreate-t Qt-simple qttest

We noticed that there is a directory named data under qttest, which contains related desktop files and icons and can be modified as needed.

Step 2: Use the qtcreator tool to create an RPM package

Open qttest in the QtCreator tool and select Build All. We can see that the default build is created in the folder qttest-build-meego. qt does not allow the compiled folder to be placed in the source file, additional settings are required.

We can see that the qttest. spec file is generated in the qttest folder. This key RPM spec file can be modified as needed.

If we release it to the simulator through qtcreator, we notice that the execution command triggered by qtcreator is under/usr/local/bin, and we have not seen any modifications there, if it must be released through qtcreator and tested, we need to modify qttest. pro file and qttest. desktop file to set a new execution path.

We enter the relevant interface and we can see that qttest has been released, such:

 

 

Related Links: My meego/moblin articles