This article is intended as a guide to help you use the Intel® Software Development Tool Suites for Intel® Atom™ Processor together with a MeeGo* 1.0 image running inside a QEMU* or KVM* virtual machine. The Intel® Software Development Tool Suites for Intel® Atom™ Processor offer two distinct options for tight integration of Intel's development tools with MeeGo*'s development and testing environment. The MeeGo* SDK development options that this tool suite integrates with are outlined at http://wiki.meego.com/SDK/Docs/1.1/MeeGo_developer_story.
You can download an existing MeeGo* image from http://www.meego.com for development and testing on this image and install target specific components of the Intel® Application Software Development Tool Suite into it. Alternatively you can also download and install the MeeGo*Image Creator, which is part of the MeeGo* SDK from http://www.meego.com and integrate development tool suite components into it's chroot environment with Xephyr* as well as prepare the target image created by MeeGo* Image Creator to contain the Intel® VTune™ Performance Analyzer Sampling Collector (SEP) and Intel® Application Debugger debug agent (idbserver) for testing and performance tuning. (http://software.intel.com/en-us/articles/meego-integration-software-development-tool-suite-atom/)

In this article we will focus on the first option of using the Intel® C++ Compiler and the Intel® Integrated Performance Primitives (Intel® IPP) inside QEMU* or on a small form factor target device.

Whether you intend to do most of your development on a live MeeGo* image running inside a QEMU* or KVM* based virtual machine or whether you intend to do your development in a protected jailroot/chroot environment, there are tools components that should be installed on your development host system and should be independent of your MeeGo* based Intel® Atom™ processor target.

It is recommended to register for the Intel® Application Software Development Tool Suite for Intel® Atom™ processor at /en-us/ and download it at https://registrationcenter.intel.com. It is also recommended to install at least the Intel® VTune™ Performance Analyzer and the Intel® Debugger following the steps outlined in the product installation guide Install_All.htm. This will take care of installing the host components to take advantage of the Intel® Application Software Development Tool Suite's performance analysis, tuning and debug capabilities.

To install the Intel® C++ Compiler and the Intel® Integrated Performance Primitives as well as the idbserver debug agent on an existing live Moblin* image please follow the steps below:

1. Open a shell on the MeeGo* image, enable root access and change to the /etc/yum.repos.d directory. There create a *.repo repository file with the following contents:

[inteltools]

name=inteltools

baseurl=http://downloads.meegozone.com/development-tool-suite

enabled=1

gpgcheck=0

A template repository file can also be found attached below.

If your network setup requires the use of a proxy server you may want to add a line with the following contents

proxy=http://myProxyIP:myProxyPort/

where myProxyIP and myProxyPort reflect the actual proxy configuration in your network environment

1. Still at the MeeGo* Linux* prompt enter the following command:

> yum groupinstall "Compiler" "IPP" "Server agent for Application Debugger"

and follow the installation messages.

This will install the Intel® C++ Compiler, the Intel® Integrated Performance Primitives (Intel® IPP) and the Intel® Application Debugger idbserver debug agent on the MeeGo* image to be used there locally.

1. To additionally install the Intel® VTune™ Analyzer Sampling Collector (SEP) you would download it directly from http://downloads.meegozone.com/development-tool-suite/rpm/vtune91u8_target.tar.gz and unpack it and install it in the MeeGo* environment. Please be advised that using SEP is only supported on real Intel® Atom™ processor based hardware and not on OS images running under KVM*.
2. To use the Intel® Application Debugger to connect to idbserver running inside KVM* and attach to processes running on MeeGo* there you will need to redirect TCP/IP port 2000 to point at KVM*:

> qemu-kvm my_meego_image.raw -redir tcp:2000::2000