Revision as of 06:11, 29 June 2012

Tools

Getting started with Mer development requires some basic tools. Mer provides a Platform SDK with all these tools included as they are not always present (or are modified) in other distros.

This page describes the Mer:Tools project which is where the tools are developed and managed. Most tools have their own page or are covered in other guides.

Packaged Versions

Generally packaged from Mer:Tools and Mer:Tools:Testing

 https://build.pub.meego.com/project/show?project=Mer:Tools
 http://repo.pub.meego.com//Mer:/Tools/

 https://build.pub.meego.com/project/show?project=Mer:Tools:Testing
 http://repo.pub.meego.com//Mer:/Tools:/Testing/

Releases

The Tools project does not make regular scheduled releases; instead it releases when required - this can be when just one version of a package has changed.

Tools releases are 'source only'; a release number represents a collection of tool versions. This is then built against a Mer Core release to produce an SDK release.

This approach allows the tools to be rebuilt against 'in house' forks of Mer that may have been frozen.

Release numbers

<version>.<stable/pre>.<incr>

1.0.1   Tools version 1  this is a pre-release, first try
1.0.2   Tools version 1  this is a pre-release, second try
1.1.0   Tools version 1  this is a release
...
2.1.0   Tools version 2  this is a release
...
1.1.1   Tools version 1  this is an update to release 1.1.0 (most tools, same version as 1.1.0, some incremented but some < 2.1.0)

Tools release numbers could be reduced to a mapping to a sha1 of the contents of the release source.

Release Steps

A Tools release requires reliable version control of both the code and associated packaging. This is not yet implemented and the interim solution is to publish the OBS src rpm in the SDK repo.

SDK

An SDK binary release is done directly from the OBS Tools project using the Mer release script. (see lbt branch as of 27/May/2012)

tools/createrelease.sh --conf release.tools --next --all 5.0.1

# Configuration

# List of project repo arch schedulers(: sep) to release
PROJECTS="Mer:Tools       Mer_Core_i486  i486 i586"

# Set this to 1 if there are x86 cross- binaries in the arm/mips repos
CROSS=

PUBLISH_SRC=1

# This should point to a public api
API=https://api.pub.meego.com/public

# This should permit rsync of /srv/obs/repos on the OBS be or a
# suitable publishing slave
RSYNC=rsync://cdownload.in.meego.com/repos

RELEASEDIR=~/releases
OBSDIR=~/obs-repos

# The target for the OBS MDS (rsync destination)
RSYNC_OBS_PUBLISH=

# The target for the repository (rsync destination)
RSYNC_REPO_PUBLISH=rsync://cdownload.in.meego.com/repo/releases/Mer-Tools/

# If rsync needs a password
export RSYNC_PASSWORD=xxxxxxxxxxxxxxx

This is then built into an image using the SDK. Currently this is a bit convoluted; in an SDK

osc co Mer:Tools/sdk-kickstarter-configs
osc build Mer_Core_i486  i586

Determine the build directory and obtain the correct .ks

 .../build/Mer_Core_i486-i586-sdk-kickstarter-configs/mer-sdk-i486-chroot.ks

Upload this to IMG, wait for the build and move the image to the distribution dir.

Tools for developing

osc

Use a version > 0.132

osc is used to interact with the OBS. It does:

command line functions provided by the OBS webui
check in / out of packages
submits requests
runs local builds

You may find latest builds for various distributions at http://download.opensuse.org/repositories/openSUSE:/Tools/

build

build is the actual script used by the OBS workers to build packages. It installs a clean chroot for you and runs a suitable compile command from the package.

You may find latest builds for various distributions at http://download.opensuse.org/repositories/openSUSE:/Tools/

spectacle

Spectacle creates .spec files from .yaml files. This makes is a *lot* easier to package your code.

https://meego.gitorious.org/meego-developer-tools/spectacle

cd /mer/tools
mkdir spectacle
git clone git://gitorious.org/meego-developer-tools/spectacle.git spectacle

qemu (specific snapshot)

qemu is needed for building non-native (ARM/MIPS) packages that need to execute ARM binaries.

qemu is found in the Mer:Tools project (currently on the MeeGo community OBS)

19 Nov2011 : Using 0.14.1

The OBS and IMG systems use qemu-usermode-static.

You need to install qemu-usermode-static package when you do 'osc build' for non-intel architecture and have "chroot: failed to run command `some-command': Exec format error" or "Warning: could not register binfmt handlers". As the package is statically linked, you may install OpenSUSE rpm on Fedora and it should work fine.

Tools for Image Building

kickstarter

https://meego.gitorious.org/~sage/meego-developer-tools/sages-kickstarter

cd /mer/tools
mkdir kickstarter
cd kickstarter
git clone git://gitorious.org/~sage/meego-developer-tools/sages-kickstarter.git kickstarter

mic2 / image-creator

http://meego.gitorious.org/meego-developer-tools/image-creator

cd /mer/tools
mkdir image-creator
cd image-creator
git clone git://gitorious.org/meego-developer-tools/image-creator.git image-creator

Development Tools for on Device usage

Device Memory Profiling via 'sp-smaps'

First you have to add the Mer_Extras repository to your device zypper configuration, available
<repositories> are 'Mer_Extras_armv6l', 'Mer_Extras_armv7hl', 'Mer_Extras_armv7l' and 'Mer_Extras_i568'

root@device# zypper addrepo http://repo.pub.meego.com/Project:/KDE:/Mer_Extras/<repository> Mer-Extras

Now feel free to install the 'sp-smaps' toolset

root@device# zypper refresh
root@device# zypper in sp-smaps

Usage:

Create a memory profiling snapshot:

root@device# sp_smaps_snapshot > my-memory-sp-smaps-snapshot.cap

Create a HTML report from the smaps capture:

root@device# sp_smaps_analyze my-memory-sp-smaps-snapshot.cap

Feel free to compress and copy the generates files for further analysis to a host system:

root@device# tar -cvf my-memory-sp-smaps-snapshot.tar \
  my-memory-sp-smaps-snapshot.cap \
  my-memory-sp-smaps-snapshot.html \
  my-memory-sp-smaps-snapshot.dir

root@device# bzip2 my-memory-sp-smaps-snapshot.tar
root@device# scp my-memory-sp-smaps-snapshot.tar.bz2 <your_user>@<your_host>:~/

Development of tools

The Mer tools are divided to two groups:

SDK and device side tools (Mer:Tools)
Host (Linux distribution) side tools (Project:MINT)

SDK and device side tools are compiled only against the Mer repositories. By this we try to keep the tools version's stable and avoid conflicts with the host distribution's packages (eg. Ubuntu/OpenSuse/Fedora).

The host side tools are provided for the most common Linux distributions.

Unstable SDK and device side tools are updated to Mer:Tools:Testing
Unstable host side tools are updated to Project:MINT:Testing
Packages that are shared between Mer:Tools and Project:MINT should be 'mastered' in Mer:Tools

As a developer:

Search the tool's version control location from About
Pull the tool's source code and make changes
Copy the original package to your home project in OBS
Update your changes to the OBS
Test your changes
Push your changes to the version control
Inform tools team about the changes with diff (URL to gitorious/gerrit/github diff)
The tools team will review, retest and update the tool to OBS

@@ Line 199: / Line 199: @@
 As a developer:
-# Search the tool's version control location [[:Category:About|About]]
+# Search the tool's version control location from [[:Category:About|About]]
 # Pull the tool's source code and make changes
 # Copy the original package to your home project in OBS

Tools

Revision as of 06:11, 29 June 2012

Contents

Tools

Packaged Versions

Releases

Release numbers

Release Steps

SDK

Tools for developing

osc

build

spectacle

qemu (specific snapshot)

Tools for Image Building

kickstarter

mic2 / image-creator

Development Tools for on Device usage

Device Memory Profiling via 'sp-smaps'

Development of tools

Views

Personal tools

Navigation

Search

Tools