This article focuses on how to use MeeGo SDK for Meego development on Linux. In Meego development, MeeGo SDK consists of two parts. For details about the two parts, see the following.
Use MeeGo SDK for Meego development on Linux
1 Introduction:
MeeGoSDK consists of the following parts:
1. A MeeGochroot environment that contains a MeeGo application Simulator Based on Xephyr (http://www.freedesktop.org/wiki/Software/Xephyr) that only supports Linux), some scripts that start/stop MeeGo desktops in Xephyr, and QtCreator that can remotely configure and deploy the MeeGo device.
2. Start the MeeGochroot environment and run the meego-sdk-chroot script of the simulator and QtCreator.
To install MeeGoSDK, download the package version of these components. This will be discussed in the next section.
2Meego development system requirements:
To run the MeeGo simulator in Xephyr, you need a newer Linux release, such as Fedora11, Ubuntu9.10) and Intel hardware environment. The hardware environment has the following requirements:
* CPU: 32 bitIntel (r) Atom (tm) orIntel (r) Core (tm) 2CPU (supportforSSSE3)
* Note: The MeeGo simulator cannot run on a CPU that does not support SSSE3.
* A compatible Intel graphics card. GMA-500, Nvidia, and ATI chipset are not supported
This is the MeeGo simulator requirement, not the SDK requirement. I can run the MeeGoSDK on the AMD processor and NV graphics card and compile/debug the program normally .)
3. Install the MeeGochroot Environment
MeeGochroot is a large file close to 800 mb ). It not only includes all the library files of MeeGo itself, but also some other useful things (Xephyr, scripts, QtCreator ).
Download the MeeGochroot compressed package: wgethttp: // download3.meego.com/meego-sdk-0524.tar.bz2
Decompress the MeeGochroot package file: tarjxvfmeego-sdk-0524.tar.bz2
// Another solution is to create a MeeGochroot by yourself. For more information, see BuildingaMeeGochrootonLinux.
4 install the meego-sdk-chroot script
The meego-sdk-chroot script sets the mount point of the chroot environment and starts the root environment in an appropriate way. When Meego development leaves the chroot environment, it will also try to uninstall the entire environment correctly and clear the processes started in the chroot environment.
Download:
Wgethttp: // sdk. download. location/meego-sdk-chroot
Execute the script:
Chmod + xmeego-sdk-chroot
Move to/usr/bin:
Mvmeego-sdk-chroot/usr/bin
Configure the host for the simulator
The next step is to configure the X environment of the host so that the simulator runs in the chroot environment) can be correctly displayed on the screen of a Common User:
Xhost + local :( here I run xhost + local: not successful. I use xhost + SI: localuser: root
Xhost + SI: localuser: your user name. OK)
After each restart, you must perform this step before running the simulator and QtCreator)
5Meego development enters the MeeGochroot Environment
The meego-sdk-chroot script sets up a MeeGochroot environment and gives you a shell in this environment:
Sudomeego-sdk-chroot ~ Meego-sdk-0524
Replace the above '~ with your chroot directory '~ /Meego-sdk-0524)
Note that this script uses the chroot command. Sometimes, the root user cannot locate this command in the PATH environment variable in Fedora, And the chroot command is in the/usr/sbin PATH ). You can add an alias line at the top of the meego-sdk-chroot script to solve this problem:
Aliaschroot = '/usr/sbin/chroot'
After the script is run, the following content is output:
- mount--bind/proc/home/ell/meego-sdk-0524/procmount--bind/sys/home/ell/meego-sdk
-
- -0524/sysmount--bind/dev/home/ell/meego-sdk-0524/devmount--bind/dev/pts/home/ell/meego-sdk
-
- -0524/dev/ptsmount--bind/tmp/home/ell/meego-sdk-0524/tmpmount--bind/var/lib/dbus/home/ell/meego-sdk
-
- -0524/var/lib/dbusmount--bind/var/run/dbus/home/ell/meego-sdk
-
- -0524/var/run/dbuscp/etc/resolv.conf/home/ell/meego-sdk
-
- -0524/etc/resolv.confroot@meego-netbook-sdk:/#
-
Install other software
You can install the software normally in the chroot environment and the latest netbook image ).
Go to the chroot environment and run: zypperinstall <package>
The following command updates the entire MeeGo image to the latest version:
- zypperdist-upgrade
-
- --------------------------------------------------------------------------------
-
- SettinghostdisplaybeforerunningSimulator
- XephyrdoesnotseeDISPLAYenvvariablefromhostsystemsinceitisrunningaschroot.Aschroot,setDISPLAYvariablebeforerunning"startmeego"thatcallsXephyr.
-
-
- exportDISPLAY=:0--------------------------------------------------------------------------------
-
6. Run the simulator.
In the chroot environment, run startmeego & as the root user &
This will start the Xephyr server and run a script. This script starts a MeeGo desktop in Xephyr.
If you want to start a program in the chroot environment and display it in the simulator window, you can:
DISPLAY =: 2glxgears replace glxgears with the program name you want to start)
Debugging in the simulator
If a problem occurs in your simulator, you can use the debug script to see what happened: startmeego-debug
This script will output some information in the console, which should give you clues to the problem.
NetbookUX interface in the simulator
It looks like this: Missing graph)
Detected problems: *. Some tool bar components dependent on the gauge, such as battery and network, cannot report the working status of the device.
7. Stop the simulator
To stop the simulator, you only need to leave chrootshell: exit
This will stop all processes started by the simulator and uninstall the path used by the chroot environment. This will output the following information:
- exitumount/home/ell/meego-sdk-0524/procumount/home/ell/meego-sdk
-
- -0524/sysumount/home/ell/meego-sdk-0524/dev/ptsumount/home/ell/meego-sdk
-
- -0524/devumount/home/ell/meego-sdk-0524/tmpumount/home/ell/meego-sdk
-
- -0524/var/lib/dbusumount/home/ell/meego-sdk-0524/var/run/dbus
-