Meego Wiki
Views

SDK/Docs/1.0/MeeGo SDK with Xephyr

From MeeGo wiki
< SDK | Docs | 1.0
Revision as of 19:54, 2 August 2010 by Bspencer (Talk | contribs)
Jump to: navigation, search

The MeeGo SDK with Xephyr provides a development environment on Linux workstations for Netbook and Handheld applications.

  1. Check for Intel graphics chipset
    2. $ lspci | grep VGA

    Desired output: 00:02.0 VGA compatible controller: Intel Corporation ...

    If your system does not have Intel graphics, see the other SDK options.

  2. Download the MeeGo SDK Image for your target as described on the Getting Started page.
  3. Install the meego-sdk-chroot script

    4. The meego-sdk-chroot script sets up mountpoints for the chroot environment, then starts the chroot proper; it also attempts to unmount everything when it exits and clear up any processes started in the chroot. Get it with: 

    $ wget http://download3.meego.com/meego-sdk-chroot

    Make the chroot script executable: 

    $ chmod +x ./meego-sdk-chroot
  4. Configure X on the host to allow Xephyr to access the display
    5. $ xhost +SI:localuser:<user name>

    Example for user named "bob": 

    $ xhost +SI:localuser:bob

    (You need to do this once before running Xephyr or Qt Creator after each reboot)

  5. Mount and "Change root" into the MeeGo image

    6. Create a directory for the MeeGo image contents: 

    $ mkdir <image destination directory>

    Mount the image into the directory: 

    $ sudo mount -o loop,offset=512 <image file> <image destination directory>

    Change the root of the terminal to the MeeGo OS root: 

    $ sudo ./meego-sdk-chroot <image destination directory>

    Example: 

    $ sudo mkdir /opt/meego-handset
$ sudo mount -o loop,offset=512 ./meego-handset-ia32-1.0.80.9.20100706.1-sdk-pre0721.raw /opt/meego-handset
$ sudo ./meego-sdk-chroot /opt/meego-handset

    The output from running meego-sdk-chroot should look like this: 

    mount --bind /proc /home/ell/meego-sdk-0524/proc
mount --bind /sys /home/ell/meego-sdk-0524/sys
mount --bind /dev /home/ell/meego-sdk-0524/dev
mount --bind /dev/pts /home/ell/meego-sdk-0524/dev/pts
mount --bind /tmp /home/ell/meego-sdk-0524/tmp
mount --bind /var/lib/dbus /home/ell/meego-sdk-0524/var/lib/dbus
mount --bind /var/run/dbus /home/ell/meego-sdk-0524/var/run/dbus
cp /etc/resolv.conf /home/ell/meego-sdk-0524/etc/resolv.conf
root@meego-netbook-sdk:/#

    Note: meego-sdk-chroot uses the chroot command. Be sure it is in your path or create an alias: 

    $ alias chroot='/usr/sbin/chroot'

    Contents

    Installing other software

    It's possible to install software from the standard locations (at least it is in netbook images) into the chroot.

    Enter the chroot, then run: 

    zypper install <package>

    It should also be possible to upgrade the whole MeeGo image using: 

    zypper dist-upgrade

    Setting host display before running Simulator

    Xephyr does not see DISPLAY env variable from host system since it is running as chroot. As chroot, set DISPLAY variable before running "startmeego" that calls Xephyr. 

    export DISPLAY=:0

    Run the Simulator

    From inside the chroot, as root do: 

    startmeego &

    This starts the Xephyr server then runs a script to boot the MeeGo desktop into it.

    Note: Currently, the simulator runs only on host systems with an Intel integrated graphics controller. It does not run with ATI or NVIDIA graphics controllers.

    If you want to run applications from the chroot and have them display in the Simulator window, you can do: 

    DISPLAY=:2 glxgears

    (replacing glxgears with the command you want to run).

    Debugging the Simulator

    If you are having issues with the Simulator, use the debug script to see what's happening: 

    startmeego-debug

    This shows the console output from the script, which may give you some clues if it's not working correctly.

    Netbook UX in the Simulator

    Here's what it looks like:

    Simulator running netbook ux.png

    MeeGo Handset UI in QEMU
    MeeGo Netbook UI in QEMU

    Known issues:

    • Panels which rely on DBus (like the battery, networking) don't report devices properly.

    Stop the Simulator

    To stop the Simulator, just exit the chroot shell with: 

    exit

    This closes down any processes started inside the Simulator and unmounts directories used by the chroot environment. The output should look something like this: 

    exit
umount /home/ell/meego-sdk-0524/proc
umount /home/ell/meego-sdk-0524/sys
umount /home/ell/meego-sdk-0524/dev/pts
umount /home/ell/meego-sdk-0524/dev
umount /home/ell/meego-sdk-0524/tmp
umount /home/ell/meego-sdk-0524/var/lib/dbus
umount /home/ell/meego-sdk-0524/var/run/dbus

    Another language version of this page

Retrieved from "http://wiki.meego.com/SDK/Docs/1.0/MeeGo_SDK_with_Xephyr"
Personal tools