Maemo Wiki Mirror - User contributions [en]

Packaging

2010-10-13T18:37:43Z

86.202.50.113: /* Testing your package */

== Creating Packages for Maemo ==

Since Maemo is based on the Debian operating system, creating packages for Maemo borrows a lot of tools and techniques from Debian.

=== Further reading ===

The following list of resources gives in-depth information on packaging in Debian and Maemo. These links largely discuss packaging Python apps but can be used for any programming language.

* [http://www.openismus.com/documents/linux/automake/automake Using automake and autoconf with C++]: A great beginner's tutorial on using autotools to create an easily packagable application
* [http://www.debian.org/doc/maint-guide/ Debian New Maintainers Guide]: The best place for information if you have never built a .deb before
* [http://wiki.debian.org/Teams/PythonModulesTeam Debian's Python Modules Team]: definitive documentation for packaging Python modules for Debian
* [http://python-modules.alioth.debian.org/python-modules-policy.htm Python Modules Policy]: Reference document.
* [http://showmedo.com/videos/video?name=linuxJensMakingDeb Creating debs on Ubuntu]: A great screencast and tutorial showing how to package a simple python application as a deb on Ubuntu!
* [https://wiki.ubuntu.com/PackagingGuide Ubuntu Packaging Guide]
* [[Documentation/Maemo 5 Developer Guide/Packaging, Deploying and Distributing | Deploying and distributing software on Maemo 5]]: Detailed documentation on packaging for Maemo, including how to ship your software afterwards
* [http://www.forum.nokia.com/Tools_Docs_and_Code/Documentation/Maemo.xhtml Forum Nokia developer documentation]: General developer documentation reference
* [[Port an existing Debian package]]
* [[Packaging a Qt application]] and how it differs from the packaging described here
* [[User:Jebba]] has created a [[User:Jebba/Package Building HOWTO | package building howto]] with details on every step

==== Checking Maemo Packages ====

Lintian dissects Debian packages and reports bugs and policy violations.
It contains automated checks for many aspects of Debian policy as well as some checks for common errors. Unfortunately it does not check conformance to the additional Maemo policy.

Currently Maemo is creating [[Maemian]] to check its policy.

== A concrete example - hello ==

=== Prerequisites ===

For the purposes of our article, we will be packaging a simple [[Hildon]] hello-world application. This will be a standard source tarball using [[Documentation/Maemo 5 Developer Guide/GNU Build System#GNU Autotools|autotools]]. For further information, you can follow [http://www.openismus.com/documents/linux/automake/automake this detailed tutorial] on using Autotools for C++ projects.

You will need a working [[Documentation/Maemo 5 Final SDK Installation|Maemo 5 SDK]] and the <code>libhildon1-dev</code> package, version 2.2 or greater, which can be installed in Scratchbox with the command:

fakeroot apt-get install libhildon1-dev

==== hello.c ====

The only C file in our project is <code>hello.c</code>:

<source lang="c">
#include <hildon/hildon.h>

int main(int argc, char *argv[])
{
GtkWidget *window;
GtkWidget *label;

hildon_gtk_init(&argc, &argv);

window = hildon_window_new();
label = gtk_label_new("Hello world!");

g_signal_connect(G_OBJECT (window), "destroy", G_CALLBACK (gtk_widget_destroy), NULL);
gtk_container_add(GTK_CONTAINER(window), label);
gtk_widget_show_all(window);

gtk_main();
return 0;
}
</source>

==== Autotools ====

{{main|Documentation/Maemo 5 Developer Guide/GNU Build System}}

The rest of the project is a small number of files to allow us to make a standard "<code>./configure && make && make install</code>" project with automake, aclocal and autoconf.

Using the autotools for packaging is quite simple for small projects. You need two files to define the structure of your project, <code>Makefile.am</code> and <code>configure.ac</code>.

<code>configure.ac</code> is a file used by automake and autoconf to generate the configure script, define the version of the resulting .tar.gz and include the tests which we need to ensure the presence of the appropriate versions of dependencies. Since <code>hello.c</code> is so simple, we only need to check for the standard C library and a C compiler, and for the Hildon library. The Hildon library check is done by <code>pkg-config</code>, which makes it easy to check the library version, and get the right compiler and linker flags. The only output file generated by the configure script will be <code>Makefile</code>, from the input file <code>Makefile.in</code>, which is in turn generated from <code>Makefile.am</code>

<source lang="autoconf">
AC_INIT([hello], [0.1])
AM_INIT_AUTOMAKE([foreign])
AC_PROG_CC
PKG_CHECK_MODULES([HILDON], [hildon-1 >= 2.2])
AC_CONFIG_FILES([Makefile])
AC_OUTPUT
</source>

<code>Makefile.am</code> defines the source structure of your project, listing the files to be installed, the binaries and object files to be generated, and the relationship between the binaries and source files.

You can see that our <code>Makefile.am</code> is very simple, defining one source file, and one binary file. The "_SOURCES" line must start with a binary name from "bin_PROGRAMS" to make the link between the source file and the executable. The "_CPPFLAGS" and "_LDADD" lines take the Hildon preprocessor and library flags that are provided by <code>pkg-config</code> in <code>configure.ac</code>.

bin_PROGRAMS = hello
hello_SOURCES = hello.c
hello_CPPFLAGS = $(HILDON_CFLAGS)
hello_LDADD = $(HILDON_LIBS)

Once we have these files, we simply need to initialise our project, defining its license, and generating all of the required files for automake to do its thing. We do this by running:

autoreconf --force --install

The arguments to autoreconf copy required files to the project (including generic install instructions and a license).

Pay attention during the execution of autoreconf, the execution should be entirely silent if it runs correctly. If there are messages, read them and do what is required to address the issues.

Now to build your software, you have a standard configure script and can simply run

./configure
make
make install

and to build a distribution file, you have

make dist

which will create a file ''<code>hello-0.1.tar.gz</code>'', which you can use for the rest of this packaging tutorial.

=== Packaging a .deb ===

The easiest way to package a .deb file is to use Debian's build helpers.

Package your application as you would distribute it in a .tar.gz (when using autotools, this is done with "<code>make distcheck</code>"). In our example, we uncompress <code>hello-0.1.tar.gz</code>, and change the current directory to <code>hello-0.1</code>.

$ tar xfz hello-0.1.tar.gz
$ cd hello-0.1

Then we run <code>dh_make</code>, which initialises the Debian package management file structure (among other things):
$ dh_make -e <my email address> -f ../hello-0.1.tar.gz -c GPL

You can of course choose a different licence for your package.

Answer the resulting questions - in this case, we are packaging a single binary.

We can now edit the files in the <code>debian/</code> directory which has been created to their desired values, before packaging the software. In fact, we can delete many of these files. All of the files ending in “.ex” or “.EX” are example files, intended to help you package different types of software.

If you use a standard configure script, you do not need to modify any files except <code>debian/control</code>, where the Hildon build-time dependency should be added. Change the <code>Build-Depends</code> line to read (by adding "<code>libhildon1</code>" at the end):

Build-Depends: debhelper (>= 5), autotools-dev, libhildon1 (>= 2.2)

Before creating a .deb, you should set a changelog entry. .deb changelogs follow a special format, so rather than editing the files by hand, use the dch helper application. This will allow you to add what new features went into this application, give credit, and so on. It is an especially important file because it sets the version and revision of the source and binary packages. On saving, a syntax check is performed which ensures that the resulting file is OK. The file format is completely documented in the [http://www.debian.org/doc/maint-guide/ Debian packaging guide].

Finally, we generate a .deb from the source code using the command:
dpkg-buildpackage -sa -rfakeroot -k<my email address>

You should now have several files created in the parent directory to where you unpacked the source code. I have;

hello_0.1.orig.tar.gz
hello_0.1-1_i386.deb
hello_0.1-1.diff.gz
hello_0.1-1.dsc
hello_0.1-1_i386.changes

Now change the target architecture to <code>ARMEL</code> and rebuild it, to generate <code>hello_0.1-1_arm.deb</code>:

sb-conf se FREMANTLE_ARMEL
dpkg-buildpackage -sa -rfakeroot -k<my email address>

==== Additional information ====

===== Ignoring git metadata =====

If you use git then you may not want to include the entire git repo in your source bundle. With dpkg-source version 1.13.25 the -i option is not git-aware so you can do:

dpkg-buildpackage -rfakeroot -sa -i -I.git

===== Adding build-time dependencies =====

If your program uses another library, such as Hildon in the above example, then both the Debian package and the configure script must depend on the library.
Otherwise, since the autobuilder only installs packages explicitly required to build your package, the build will fail.

Often, the Debian package has a different name to the pkg-config file, just like in the Hildon example. One way to check which package owns a pkg-config file is to use <code>dpkg-query</code> on the pkg-config file, for example the <code>mafw</code> pkg-config file (notice the extra <code>.pc</code> file extension):
dpkg-query --search mafw.pc
which looks through the installed packages and finds:
libmafw0-dev: /usr/lib/pkgconfig/mafw.pc
Then you know that you must add <code>libmafw0-dev</code> to the <code>Build-Depends</code> line in <code>debian/control</code> if you use the <code>mafw</code> pkg-config file in <code>configure.ac</code>.

===== Checking build-time dependencies =====

You may verify that your <code>Build-Depends</code> field in debian/control is complete by running:

dpkg-depcheck -m dpkg-buildpackage -rfakeroot -b

in the source tree. (You will need to <code>fakeroot apt-get install devscripts</code> for this to work).

=== Testing your package ===

The first place you can test your app is in Scratchbox. Start Xephyr and the Maemo GUI as described in [[Documentation/Maemo 5 Final SDK Installation | the Maemo 5 SDK instructions]], then run your application by hand from within Scratchbox.

Once you have created a .deb armel package of your application, you can also test it on your N900. Copy the .deb file to the device, and install it by selecting it in the file manager. You will need to ensure that the OS version on your device is compatible with the development environment in your Scratchbox.

To make the package installable using Hildon Application Manager (which will get launched when you select the package), you should follow the [[#Maemo-specific packaging information]] below. In particular, you must set the "Section" to one of the valid sections below in the "debian/control" file.

Once the package is installed, you will be able to launch it directly from the command line in the Xterminal application. To get the application to appear in the application list, you will need to include an icon and desktop file in the package as described in [[/Guidelines | the packaging policy]].

=== Uploading to extras-devel ===

{{main|Uploading to Extras-devel}}

== Maemo-specific packaging information ==

=== Packaging policy ===

{{main|Packaging/Guidelines}}

Maemo packages follow the Debian Policy, but there are some items where Maemo:
* Is more strict (it is an embedded distribution)
* Is more relaxed:
** A single target device (per release)
** A single specified UI (Hildon)
** A single user
* Differs from Debian because Maemo has different:
** Objectives
** Maintainers
** Infrastructure

Most of the specifics for Maemo packaging are outlined in the [[/Guidelines|Maemo packaging guidelines]].

=== Sections ===

This is the list used in Fremantle/Maemo5 and is the same as the [http://lists.maemo.org/pipermail//maemo-developers/2008-October/035437.html final] list for Diablo as [[Task:Package_categories|discussed in the task]] and [[Packaging/Guidelines#Sections|outlined in the packaging guidelines]].

{| class="wikitable"
! Key
! Example English i18n
! Example apps
|-
| <code>user/desktop</code>
| Desktop
| Home, statusbar and taskbar applets
|-
| <code>user/development</code>
| Programming
| py2deb
|-
| <code>user/education</code>
| Education
| Flashcard apps
|-
| <code>user/games</code>
| Games
| Doom, Duke Nukem 3D
|-
| <code>user/graphics</code>
| Graphics
| Photo apps, GIMP, Inkscape, fonts
|-
| <code>user/multimedia</code>
| Multimedia ''or'' Sound & Video
| Canola, mplayer, Kagu, UKMP, MediaBox
|-
| <code>user/navigation</code>
| (Location &) Navigation
| maemo-mapper, Navit
|-
| <code>user/network</code>
| Internet & Networking
| Web browsers, Samba clients, OpenAFS, Transmission
|-
| <code>user/office</code>
| Office
| GPE, Claws, AbiWord
|-
| <code>user/science</code>
| Science
| gnuplot, Octave
|-
| <code>user/system</code>
| System
| rotation-support, enhanced kernels, themes
|-
| <code>user/utilities</code>
| Utilities ''or'' Accessories
| Calculators, terminals, text editors
|}

If the package's section starts "user/", but is not any of the above, the ''Application Manager'' forces them into an "Other" section.

=== Desktop files ===

{{main|Desktop file format}}

Desktop files are used for application icons in menus on the Linux desktop. The Maemo application menu uses the same desktop files, but installs them to a slightly different location; <code>/usr/share/applications/hildon</code> instead of <code>/usr/share/applications</code>. You can add the desktop file to the <code>.install</code> file for your application so that it is installed to the correct place, for example, if you have <code>debian/application.install</code>, adding the line:

application.desktop usr/share/applications/hildon

would install <code>application.desktop</code> to the correct location. The location is also available with <code>pkg-config</code>, for example:

pkg-config --variable=desktopentrydir osso-af-settings

which can be used in a Makefile to install the desktop file to the correct location.

There is some official documentation on [[Documentation/Maemo_5_Developer_Guide/Application_Development/Writing_a_new_maemo_application#Adding_application_to_menu|desktop files for Maemo applications]].

=== Maemo-specific fields ===

There are a number of Maemo-specific package fields that are handled by Application manager. The Application manager documentation [http://hildon-app-mgr.garage.maemo.org/packaging-stable.html outlines] them.

==== Displaying an icon in the Application Manager next to your package ====

Displaying an icon in the Application Manager next to your package makes it look pretty and makes your package stand out, and it is not that hard to do.

# Make an image that is '''48x48''' pixels. The image can be saved in any format that is supported by GdkPixbufLoader on Maemo, but PNG is commonly used.
# base64 encode the image. This can be done in many ways, depending on the platform, but assuming you are in scratchbox:
<pre>
apt-get update
apt-get install sharutils
uuencode -m <name of 48x48 image> <name of 48x48 image> > <name of 48x48 image>.base64
</pre>
# Add the field ''XB-Maemo-Icon-26'' to your <code>debian/control</code> (in Maemo4 the size of the icons was 26x26, hence the name of the field, '''which has not changed''')
# Open the base64 version of your image and copy from the line under ''begin-base64 644 <name of 48x48 image>'' to the line above the ''===''
# Add this to the ''XB-Maemo-Icon-26'' field
# Add a space in front of every line of the encoded icon. You can do that automatically using sed when you base64 encode the image:
<pre>
uuencode -m <name of 48x48 image> <name of 48x48 image> | sed -e s,^,\ , > <name of 48x48 image>.base64
</pre>

Here is an example of a properly formatted Maemo-Icon-26: (of wrong image size)
<pre>
Description: Chess...
XB-Maemo-Icon-26:
iVBORw0KGgoAAAANSUhEUgAAABoAAAAaCAYAAACpSkzOAAAABGdBTUEAAK/INwWK6QAAABl0
RVh0U29mdHdhcmUAQWRvYmUgSW1hZ2VSZWFkeXHJZTwAAALxSURBVHja3FZNTBNREP669J/S
XYxtKRWl1JOSFBIPhkitCQeNiaKBmzdj9Ggk0ZOBxHDWixcTjV6MF+WiIB40YEyMBMGYEqQK
tLS2lG7pdre0pF3WtxslgJRuD2J0kpfdTN7O976Z782sRpIk7IZR2C2TGW1cv8xaY5WuXLy8
iW5XV5fk8/kkr9e7ya/T6SSNRiOViikvbbmDDD590SusZBGYDiDwJbDud7vdvYIgIJfLYXV1
tSwhrQrSfRX6/26N/j+gkjW6ce06HE4HGEctGuj9oEwUzFYz5ubmEA6HQVEUisUi8vn8b4rd
zjRbNxCZrr+3t7XTzjrnvMfdxMi7xj6OIRaPIbWcQjabVdRWKBTkrX4SZ2SjvCtKXf+tkxxD
M5MetwfHj/lwwueHy+WCVqvdehdHKq7R6JvbpfNMAGiGhs1mg9ls3sS+4hodbDqCwef9mA9P
7vhhVVWV3BGUOomiaCSufEWMxNwimlweMFYbpoMfyp70J6t8xanLZgWs8Ak07N0Hau0P3qOs
wIHnl5FJx2E1WlUFuXrzIS713KusRplMCoLAgl2O4N34ODQ4VRaot6cbUzMRNNQ/w/uJWXWM
eH5JARkYHsLQMIe1NZEpB7Sn1uKFhkL3maO4cL5NHVAo+hkPnrzEq2HqQIf/3ICzvr7FXmeH
3qBXlslkgtFoVBS3YfbcKRRFfJpagE6vUwd0//FbjI7mkcvnGoNfg51ORx3sNju+hWYxMxsk
jHlF2jJgdXU1DAaDrDx/kQAVRREJlldXo8kJoPlQ8wHSevosFgs5MmE5H0IingDP8eAzPAQC
tkJakDz05Hsks+poPzwg6+Luo9chVb2O3Hilv7V6W5nO02cVX3wxjsj3CMKRBUSjUcQWY0iy
SQVoi6XJaiQxubKpI02yj2xk6BoaBr0BqXRKCZpYSiCZlIXCguM4pWtvY0ypyUtt87PSIj/t
pJ/JICzLKiBLySTYVArpdFrp3DuMhRZVqfvnJ+wPAQYA1hdr5EDqltYAAAAASUVORK5CYII=
</pre>

Please note that if you are packaging a command-line only program that can be executed by the user, you should use the [[User:Tanner#CLI_icon|CLI icon]] only.

==== Bugtracker location ====

As a requirement for your package being promoted from [[Extras-testing]] to [[Extras]], your <code>debian/control</code> file must have a link to a bugtracker, which is visible in the [http://maemo.org/packages/ maemo.org packages interface]. It is possible to [[Bugs:Adding Extra products|request a component at bugs.maemo.org]] or use a [[Getting_started_with_Maemo_Garage#Trackers_and_tasks|Garage project bugtracker]], or even an email address.

Add the field ‘XSBC-Bugtracker’ to your <code>debian/control</code>, for example:
XSBC-Bugtracker: https://bugs.maemo.org/enter_bug.cgi?product=mypackage

Alternatively for e-mail addresses, you can use the following format:
XSBC-Bugtracker: mailto:yourname@example.com

==== Pretty names ====

A package can specify a pretty name for itself. This name is displayed in the Application manager UI instead of the real package name.

The pretty name is specified with the '<code>XSBC-Maemo-Display-Name</code>' field in your <code>debian/control</code> file, for example:
XSBC-Maemo-Display-Name: My package name

==== Maemo revision string ====

If an upstream package is re-packaged or modified for Maemo, the Maemo revision string should be appended to the upstream revision, in the <code>debian/changelog</code> file. So if in Debian the package name was something like "Myapp-0.4-2" in maemo this package will be called "Myapp-0.4-2maemo0". The number after the "maemo" string is a progressive number.

==== Maemo upgrade description ====

Tell users what changed in the update:
XB-Maemo-Upgrade-Description: Formatted like "Description".
Will be displayed if user upgrades to new version and clicks
on "Details".
.
Human-readable and translatable.
As with all Maemo-specific fields, the "XB-" prefix is needed so the field will remain in the binary package.

==== Translations of text fields ====

The following fields can be translated to the end user's local language: Maemo-Display-Name, Description and Maemo-Upgrade-Description. It is strongly recommended to make use of this possibility so that end users understand what the application does for them while browsing through the Application Manager.

The translation is done by adding a suffix like "-de_DE" to the respective field name, where "de_DE" is the locale the translated text is for. For example, if LC_MESSAGES equals de_DE, the Application Manager first tries "Description-de_DE" to find the description of a package and then falls back to "Description".

Here's an example:
Description: Chess...
XB-Maemo-Display-Name: My package name
XB-Maemo-Upgrade-Description: Formatted like "Description".
XB-Description-de_DE: Schach...
XB-Maemo-Display-Name-de_DE: Mein Packetname
XB-Maemo-Upgrade-Description-de_DE: Formatiert wie "Description".
Note how "Description" becomes "XB-Description-xx_YY" when a locale suffix is added. This is because it's not a standard Debian field any longer.

=== Debhelper 7 ===

Since the Autobuilder's [http://www.gossamer-threads.com/lists/maemo/developers/60704 use] of the Squeeze devkit, debhelper 7 is supported natively by it.

Follow the steps on that link to also make your FREMANTLE_* target use the Squeeze devkit.

Note: dh_make doesn't seem to be provided by the Squeeze devkit, so you'll have to run it outside of Scratchbox to get a debian/ folder based on debhelper 7.

----

A backport of Debhelper 7 for Fremantle is available in extras-devel.

$ fakeroot apt-get install debhelper7

It works transparently and can coexist with debhelper 5 in the SDK. It even works on the autobuilder, if the package specifies the correct build-dependency of <code>debhelper7</code>. The following lines in <code>debian/rules</code> are necessary to use the new debhelper:

PATH:=/usr/bin/dh7:/usr/bin:$(PATH)
export PATH
SBOX_REDIRECT_IGNORE=/usr/bin/perl
export SBOX_REDIRECT_IGNORE

In debian/control change:

Build-Depends: debhelper (>= 7) [...]

to

Build-Depends: debhelper'''7''' (>= 7) [...]

Further information about the updated debhelper is available at [[User:Tanner#debhelper7]].

If you also need a more recent [http://build-common.alioth.debian.org/ CDBS], then use the package [http://maemo.org/packages/view/cdbs-dh7/ cdbs-dh7], which conflicts with the standard CDBS and does not work on autobuilder yet.

Alternatively, you can try to use debhelper 5. Debian packages that require level 7 need some changes, for example:
* debian/compat: 7 -> 5
* debian/control: Build-Depends: debhelper (>= 7) -> debhelper (>= 5)
* Possibly, comment out a few dh_* calls from debian/rules, which might not exist on level 5

Things might get complex if the packaging already uses some new features of level 7, like CDBS-style helper rules. In such cases, looking at versions of packages written prior to the compatibility level upgrade might help doing the downgrade (and most Debian packages are kept in public SCMs like svn.debian.org).

=== Ovi Store publishing ===

{{main|Ovi Store publishing}}

[[Category:Packaging]]

Documentation/Maemo 5 Final SDK Installation

2010-10-12T11:09:30Z

86.202.50.113: /* Starting/Shutting down the SDK UI */

==Introduction==

The following document describes the installation of the Maemo 5 Final SDK. Maemo SDK uses Scratchbox as the cross compilation environment into which Maemo specific development files are installed.

Before we begin with the installation, have a look at the minimum system requirements. We officially support x86-32 Debian based distributions, mainly Debian and Ubuntu though it is possible to install the SDK on other flavours of Linux too.

Once you are sure that your development machine fulfils these requirements, you can proceed with the following guidelines:

Maemo 5 SDK comes with two command-line installation scripts and GUI installer (beta) to ease the SDK installation.
* Scratchbox installer script which downloads and installs the required version of Scratchbox onto your host machine.
* Maemo SDK installer which sets up two targets (armel and x86) inside Scratchbox, downloads the minimal rootstraps for both targets, and installs the open source development files based on the user selection during the installation process.
* GUI installer which combines both Scratchbox and SDK installation.

Maemo 5 SDK also provides the essential Nokia proprietary binary packages needed for Maemo development and additional Nokia applications in an authenticated repository. In order to have access to this repository, you will need to accept the End User License Agreement (EULA).   For the complete functionality and usability of the Maemo SDK, it is required to install Nokia proprietary binary packages in addition to the open source packages.

===What is not included in the Maemo SDK?===

Xephyr X11 server software is needed on your host machine before you can run any applications in the Maemo SDK. It is an X11 server that provides a device screen for the developer so that you can see all the Maemo application windows and visuals on your host machine. This software is not included in the SDK mainly because it is available on most linux distributions.

If you choose to install Maemo SDK using the GUI installer on Debian based systems, it will provide an option to install Xephyr for you.

If not, you can manually install Xephyr as follows:

On Debian based linux systems, Xephyr can be installed outside Scratchbox environment using apt with root permission:

$ sudo apt-get install xserver-xephyr

On a Gentoo system you need to install xorg-server with the kdrive useflag. This builds the Xephyr binary.

==Installing Maemo 5 SDK using GUI Installer==

Maemo 5 SDK installation is now made easy with GUI installer. This
installer will install Scratchbox and Maemo 5 SDK on Debian based
systems. This installer will allow installation of nokia closed packages and
applications provided that EULA at [http://tablets-dev.nokia.com/eula/index.php this webpage] is accepted.

===Features of the GUI installer===

* Install/Upgrade Scratchbox
* Installation of Maemo 5 SDK
* Installation of nokia-binaries
* Installation of nokia-apps
* Installation of Xephyr, if missing
* Can create a launcher for Xephyr on Desktop
* Can create a shortcut to Scratchbox home folder on Desktop
* Can create Maemo 5 info page on Desktop that contains useful links for developers
* Uninstallation of Scratchbox and targets (Debian-based distros only)

GUI installer offers standard and custom installation modes in a wizard. Standard installation will use default settings, while custom offers more choices. Please note that standard mode will overwrite any of the standard targets (<code>FREMANTLE_X86</code>, <code>FREMANTLE_ARMEL</code>) if present, but contents of Scratchbox home will be preserved. Please use the custom mode if you don't want to overwrite your targets.

The GUI installer Qt application requires Python bindings for Qt. GUI installer can install the required packages if not already installed.

The installer will use the <code>http_proxy</code> environment variable if available. If your connection does not seem to work, you will be asked to manually enter proxy settings.

GUI installer has been tested on Ubuntu Karmic and Debian Lenny, both 32bit and 64bit versions. The GUI installer needs to download Maemo SDK so it requires a working Internet connection. On 64bit kernel, you need to disable VDSO for 32bit applications manually.

===Starting installation with GUI installer===

There is some missing options in this Python script if you run from non-Debian Linux systems you got errors, because it will not automatically define the installation path of Scratchbox, to correct this errors you must patch this script.

Also you must uncheck the Xephyr checkbox and install it manually.
<source lang="diff">
129c129
< SB_PATH = "/scratchbox"
---
> SB_PATH = "/opt/scratchbox"
2297a2298
> opt = opt + "-s /opt/scratchbox"
2351a2353
> cmd = cmd +" -s /opt/scratchbox"
</source>

wget http://repository.maemo.org/stable/5.0/maemo-sdk-install-wizard_5.0.py
chmod a+x maemo-sdk-install-wizard_5.0.py

$ Installer requires root privileges
Ubuntu
sudo ./maemo-sdk-install-wizard_5.0.py
Debian
su -c ./maemo-sdk-install-wizard_5.0.py

===Limitations of the GUI installer===

* As the installer will do package installation, you should quit all package managers before running it.
* Please note that detecting Scratchbox is not perfect and it will detect only if it is installed in the <code>/scratchbox</code> path.
* Please note that python-qt features used in this installer might not be available in older Ubuntu and Debian distros.
* Due to differences in versions of Python Qt bindings, certain parts of installation can work differently on different systems.
* Installer only shows required settings on 64-bit machines but does not add them automatically.
* Installer will always use DISPLAY :2, if you want to use a different value, you need to change it manually.
* GUI installer does not work on SUSE Linux. You can use command line installers instead.

==Installing Maemo 5 SDK on x86-32 Debian based distribution==

1. Download the Scratchbox installer and the Maemo SDK installer scripts. These are the same scripts as are available through Forum Nokia: [http://www.forum.nokia.com/Tools_Docs_and_Code/Tools/Platforms/Maemo/ Maemo SDK at Forum Nokia].

$ wget http://repository.maemo.org/stable/5.0/maemo-scratchbox-install_5.0.sh http://repository.maemo.org/stable/5.0/maemo-sdk-install_5.0.sh

2. Set the permissions to execute the scripts.

$ chmod a+x ./maemo-scratchbox-install_5.0.sh ./maemo-sdk-install_5.0.sh

Users of Ubuntu 10.04 LTS will need to do the following to fix the installation, note that this may reduce system security! [http://talk.maemo.org/showpost.php?p=636394&postcount=8]

$ sudo su
$ echo "vm.mmap_min_addr = 0" >> /etc/sysctl.conf
$ sysctl -p
$ exit #to go back to user

3. Run the Scratchbox installer with root permission specifying the username to be added to scratchbox users group and sbox group. The username should be an existing user name from the host Linux system. This will download about 420 MB of material from the web, which is not resumeable if interrupted.

$ sudo ./maemo-scratchbox-install_5.0.sh -u $USER

4. The installation script adds the specified user to ‘sbox’ user group. For the group membership to be effective in the current terminal session, run the following command:

Note: This command will change the existing group ID during the current login session to ‘sbox’. If you do not want this change, just logout and log back in again for the group membership to be effective.

$ newgrp sbox

At this step, you should have a working Scratchbox environment ready.

5. Proceed further to run the Maemo SDK installer script. This script is run as 'user' outside the Scratchbox environment. Set permission for 'user' before runing script.

$ sudo chmod +x ./maemo-sdk-install_5.0.sh
$ ./maemo-sdk-install_5.0.sh

If you have installed Scratchbox in a path alternative to <code>/scratchbox</code>, you will need to specify the path with ‘-s PATH’ option. More information on available command line options can be found with --help option. Follow the instructions on the go.

6. Once the script has successfully completed its execution, you can login into Scratchbox.

$ /scratchbox/login

If you are not able to login, take a look at the [[#Limitations of Scratchbox|limitations of Scratchbox]].

7. Proceed further to accept the EULA in order to obtain the Nokia proprietary binary packages. These Nokia binaries are essential for the complete functionality of the Maemo SDK.

7.1. Accept the EULA on [http://tablets-dev.nokia.com/eula/index.php this webpage] <br/>
7.2. Copy the <code>sources.list</code> entry given to you after the license acceptance to your Scratchbox x86 and armel target’s <code>/etc/apt/sources.list</code> file. Execute the commands below on the <code>FREMANTLE_ARMEL</code> and <code>FREMANTLE_X86</code> targets.

[sbox-FREMANTLE_X86: ~] > sb-conf select FREMANTLE_ARMEL
[sbox-FREMANTLE_ARMEL: ~] > nano /etc/apt/sources.list # add deb line
[sbox-FREMANTLE_ARMEL: ~] > apt-get update
[sbox-FREMANTLE_ARMEL: ~] > fakeroot apt-get install nokia-binaries nokia-apps

[sbox-FREMANTLE_ARMEL: ~] > sb-conf select FREMANTLE_X86
[sbox-FREMANTLE_X86: ~] > nano /etc/apt/sources.list # add deb line
[sbox-FREMANTLE_X86: ~] > apt-get update
[sbox-FREMANTLE_X86: ~] > fakeroot apt-get install nokia-binaries nokia-apps

The above step installs all needed Nokia proprietary binary packages along with the open source binaries that have dependencies to Nokia proprietary binary packages. With this, your Maemo 5 SDK environment is set up completely and ready for development. If you got any DNS errors with <code>apt-get install</code> resolving 'repository.maemo.org', you have to copy your host /etc/resolv.conf to Scratchbox:

$ sudo cp /etc/resolv.conf /scratchbox/etc/resolv.conf

==Installing Maemo 5 SDK on openSUSE==

There are instructions at [http://en.opensuse.org/Maemo5 opensuse.org].

==Installing Maemo 5 SDK on non-Linux operating systems==

If you do not have a Linux environment (Windows or Mac OS X), you can install a [[Documentation/Maemo_5_Developer_Guide/Development_Environment/Maemo_SDK_Virtual_Images|Maemo SDK virtual machine image]]
from [http://tablets-dev.nokia.com/maemo-dev-env-downloads.php tablets-dev.nokia.com]. [http://www.vmware.com/products/player/ VMPlayer is required].

==Starting/Shutting down the SDK UI==

Before starting the UI framework, ensure that you have installed the following:
*Xephyr X11 server on the host machine outside the Scratchbox environment
*The SDK as described above
*The Nokia proprietary binary packages

1. Now, run Xephyr outside the scratchbox environment:

$ Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -kb &

Ubuntu 10.04 users using the package in the repositories will have to run the same command without the <code>-host-cursor</code> and <code>-kb</code>, however the terminal window will have to stay open.
For recent Ubuntu releases the recommended Xephyr command line (using Finnish keyboard layout) is:

$ Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -keybd ephyr,,,xkbmodel=evdev,xkblayout=fi

2. Login to Scratchbox X86 target

$ /scratchbox/login

Welcome to Scratchbox, the cross-compilation toolkit!

Use 'sb-menu' to change your compilation target.

See /scratchbox/doc/ for documentation.

[sbox-FREMANTLE_X86: ~]>

3. Set the DISPLAY variable to match the display setting given for the Xephyr server.

[sbox-FREMANTLE_X86: ~] >export DISPLAY=:2

4. Start the UI framework .

[sbox-FREMANTLE_X86: ~] >af-sb-init.sh start

5. You will now see the UI framework up and running on the Xephyr window.

6. You can shut down the UI framework as follows:

[sbox-FREMANTLE_X86: ~] >af-sb-init.sh stop

==Installation of x86-64 Debian based distributions==

Since Scratchbox only supports x86-32 bit Linux host systems, we need to force the installation of x86-32 Scratchbox packages on the x86-64 bit machines. Using the -F option with the Scratchbox installation script can do this.

===Installation procedure===

* Download the Scratchbox installer and the Maemo SDK installer scripts.

$ wget -c http://repository.maemo.org/stable/5.0/maemo-scratchbox-install_5.0.sh http://repository.maemo.org/stable/5.0/maemo-sdk-install_5.0.sh

* Set permissions to execute the scripts.

$ chmod a+x ./maemo-scratchbox-install_5.0.sh ./maemo-sdk-install_5.0.sh

Users of Ubuntu 10.04 LTS will need to do the following to fix the installation, note that this may reduce system security! [http://talk.maemo.org/showpost.php?p=636394&postcount=8]

$ sudo su
$ echo "vm.mmap_min_addr = 0" >> /etc/sysctl.conf
$ sysctl -p
$ exit #to go back to user

* Run the Scratchbox installer script as 'root user' with -F option, specifying the username to be added to Scratchbox users group sbox group as follows:

$ sudo ./maemo-scratchbox-install_5.0.sh -F -u $USER

* If you are running squeeze or intrepid or later, read [[#Limitations_of_Scratchbox]] before continuing.

Upon successful installation of Scratchbox, continue to run the Maemo 5 Final SDK Installer as instructed in the [[#Installing_Maemo_5_SDK_on_x86-32_Debian_based_distribution|x86-32 installation]].

==Starting Scratchbox on non-Debian based systems==

If Scratchbox was installed from Debian packages, the <code>/etc/init.d/scratchbox-core</code> init script is installed and Scratchbox should start automatically when the system is rebooted. However, if you have installed Scratchbox from tarballs, then rebooting your machine will clear away all the mounts and binfmt_misc registrations that Scratchbox requires to work. To get your Scratchbox working again after reboot, you have to run the following command as root:

$ sudo /scratchbox/sbin/sbox_ctl start

Alternatively you can add <code>sbox_ctl</code> as an init script to the <code>/etc/init.d</code> directory and create the appropriate links at your system's runlevel directories. This procedure works on some systems:

$ ln -s /scratchbox/sbin/sbox_ctl /etc/init.d/scratchbox-core
$ /usr/sbin/update-rc.d scratchbox-core defaults

Refer to your system's documentation for the correct instructions.

==Upgrading from Maemo 5 Beta2 SDK==

A smooth upgrade from beta2 to Final SDK is unfortunately not possible. Hence it is advised to freshly install the Final SDK. Before you do so, read through the instructions below.

Some of the Nokia applications shipped with the final SDK use a hard coded path for user home directory which presents a problem since the default username on the device differs from the username on the developer’s machine. To make these applications work, it is required to create a home directory that matches the hard coded value. This needs to be done outside scratchbox using root privileges. The -u option in the Scratchbox installer has been updated to create the necessary symlinks. Running the installer with -u option when the Scratchbox has been already installed will just add the user and create symlinks. Running it for already existing user will check for the symlink and create it if needed.

Run the command below to create the symlink for existing Scratchbox user:

$ sudo ./maemo-scratchbox-install_5.0.sh -u <EXISTING_USER>

Alternatively, you can create the symlinks manually as follows, if Scratchbox is installed in the default location:

$ sudo ln -s /scratchbox/users/<username>/home/<username> /scratchbox/users/<username>/home/user

The Final SDK installer additionally creates a directory <code>/opt</code> under <code>/target/<target_name>/</code>.

'''Reason:''' In order to facilitate installing applications under <code>/opt</code> on the device, a symlink <code>/opt</code> has been created pointing to <code>/home/opt</code>. The SDK inherits this feature. Under Scratchbox, <code>/opt</code> points to <code>/target/links/opt</code> which in turn points to <code>/targets/<target_name>/opt</code>. Installing the rootstraps makes this point to <code>/home/opt</code>, which is not what we want, since we need <code>/opt</code> to be target specific. In order to resolve this situation, we have to manually check whether <code>/targets/<target_name>/opt</code> is a symlink and if it is, remove it and create a directory with the same name.

==Upgrading from Maemo 4.x/Diablo SDK==

Due to the fact that there are API breaks in Fremantle, we cannot upgrade Diablo SDK to Fremantle. We can however have Fremantle Scratchbox targets co-exist with Diablo targets.

For this, we need to first upgrade the Scratchbox installation on our host machine.

*Download the Maemo5 scratchbox installer.

*Set executable permissions and run it as follows:

$ chmod a+x ./maemo-scratchbox-install_5.0.sh
$ sudo ./maemo-scratchbox-install_5.0.sh -U -u <EXISTING_USER> -s /scratchbox

Once the Scratchbox installation is done, run the Maemo 5 Final SDK installer.

==Manual Installation==

===On x86 and x86_64 Debian-based systems===

* You can add the following line into your host machine's <code>/etc/apt/sources.list</code> file.

deb http://scratchbox.org/debian/ hathor main

* Install the needed Scratchbox packages with root permission

$ sudo apt-get update
$ sudo apt-get install scratchbox-core scratchbox-libs scratchbox-devkit-qemu scratchbox-devkit-debian scratchbox-devkit-doctools scratchbox-devkit-perl scratchbox-toolchain-host-gcc scratchbox-toolchain-cs2007q3-glibc2.5-arm7 scratchbox-toolchain-cs2007q3-glibc2.5-i486 scratchbox-devkit-svn scratchbox-devkit-git scratchbox-devkit-apt-https

The Scratchbox packages will be unpacked to <code>/scratchbox</code> directory and the installation procedure will ask you some questions about the group and user accounts. Default group to Scratchbox is 'sbox'.

* Users who will be using Scratchbox should be added using the following command with root permission:

$ sudo /scratchbox/sbin/sbox_adduser USER yes

It will automatically include the user to the Scratchbox group, create user directories under <code>/scratchbox/users</code> and mount several directories (<code>/dev</code>, <code>/proc</code>, <code>/tmp</code>) under the user directory.

* Some of the Nokia applications shipped with the final SDK use a hard coded path for user home directory which presents a problem since the default username on the device differs from the username on the developer’s machine. To make these applications work, it is required to create a home directory that matches the hard coded value. This needs to be done outside scratchbox using root privileges.

$ sudo ln -s /scratchbox/users/<username>/home/<username> /scratchbox/users/<username>/home/user

* For the group membership to be effective in the current terminal session, run the following command:

$ newgrp sbox

'''Note:''' This command will change the existing group ID during the current login session to 'sbox'. If you do not want to change, simply logout and log back in for the group membership to be effective.

* Log-in to Scratchbox.

$ /scratchbox/login

* Configure the scratchbox x86 and armel targets as follows:

[sbox->:~]>sb-conf st FREMANTLE_X86 -c cs2007q3-glibc2.5-i486 -d perl:debian-etch:doctools:svn:git -t none
[sbox->:~]>sb-conf st FREMANTLE_ARMEL -c cs2007q3-glibc2.5-arm7 -d qemu:perl:debian-etch:doctools:svn:git -t qemu-arm-sb

* Download the minimal rootstraps.

[sbox->:~]> wget http://repository.maemo.org/stable/5.0/armel/maemo-sdk-rootstrap_5.0_armel.tgz http://repository.maemo.org/stable/5.0/i386/maemo-sdk-rootstrap_5.0_i386.tgz

* Switch to x86 target, install the devkits, etc and fakeroot into the target, install the minimal rootstrap and finally the Maemo development files.

[sbox->:~]> sb-conf se FREMANTLE_X86
[sbox-FREMANTLE_X86: ~] > sb-conf rs maemo-sdk-rootstrap_5.0_i386.tgz

* Some users seem to have problems downloading all files with apt http pipelining enabled. If you want to make sure or you get download errors like "104 connection reset by peer" at the fakeroot steps below, then disable http pipelining with the next command:
[sbox-FREMANTLE_X86: ~] > echo 'Acquire::http::Pipeline-Depth "0";' >> /etc/apt/apt.conf.d/00maemo

* either way, continue here:
[sbox-FREMANTLE_X86: ~] > sb-conf in -edFL
[sbox-FREMANTLE_X86: ~] > apt-get update
[sbox-FREMANTLE_X86: ~] > fakeroot apt-get install maemo-sdk-debug

The meta-package <code>maemo-sdk-debug</code> installs all needed open source runtime, development and debug pakcages into the target. Use <code>maemo-sdk-runtime</code> if you want only runtime packages to be installed or use <code>maemo-sdk-dev</code> if you want only the runtime and development packages to be installed.

* Accept the EULA from [http://tablets-dev.nokia.com/eula/index.php here] to obtain the URL to access the Nokia binaries repository.

* Add the URL thus obtained to the Scratchbox target's <code>/etc/apt/sources.list</code> and do the following:

[sbox-FREMANTLE_X86: ~] >apt-get update
[sbox-FREMANTLE_X86: ~] >fakeroot apt-get install nokia-binaries nokia-apps

* In order to facilitate installing applications under <code>/opt on the device, a symlink <code>/opt</code> has been created pointing to <code>/home/opt</code>. The SDK inherits this feature. Under Scratchbox, <code>/opt</code> points to <code>/target/links/opt</code> which in turn points to <code>/targets/<target_name>/opt</code>. Installing the rootstraps makes this point to <code>/home/opt</code>, which is not what we want, since we need <code>/opt,/code> to be target specific. In order to resolve this situation,

[sbox-FREMANTLE_X86: ~] >rm -rf /targets/FREMANTLE_X86/opt
[sbox-FREMANTLE_X86: ~] >mkdir /targets/FREMANTLE_X86/opt

* Execute similar steps on the armel target too to set it up:

[sbox-FREMANTLE_X86: ~]> sb-conf se FREMANTLE_ARMEL
[sbox-FREMANTLE_ARMEL: ~] > sb-conf rs maemo-sdk-rootstrap_5.0_armel.tgz

* again,the next command disables http pipelining, if you like:
[sbox-FREMANTLE_X86: ~] > echo 'Acquire::http::Pipeline-Depth "0";' >> /etc/apt/apt.conf.d/00maemo

* pipelining disabled or not, here we go again...
[sbox-FREMANTLE_ARMEL: ~] > sb-conf in -edFL
[sbox-FREMANTLE_ARMEL: ~] > apt-get update
[sbox-FREMANTLE_ARMEL: ~] > fakeroot apt-get install maemo-sdk-debug

* Add the same URL obtained above to access the Nokia binaries repository under <code>/etc/apt/sources.list</code> file of the Scratchbox armel target.

[sbox-FREMANTLE_ARMEL: ~] >apt-get update
[sbox-FREMANTLE_ARMEL: ~] >fakeroot apt-get install nokia-binaries nokia-apps

* Create the <code>/opt</code> directory.

[sbox-FREMANTLE_ARMEL: ~] >rm -rf /targets/FREMANTLE_ARMEL/opt
[sbox-FREMANTLE_ARMEL: ~] >mkdir /targets/FREMANTLE_ARMEL/opt

With this, you must now have both the targets setup and ready to use.

[[#Starting/Shutting down the SDK UI|Start the UI framework]].

==Un-installation==

Make sure that you have no process running inside Scratchbox. Uninstalling Scratchbox will remove everything that is installed and saved inside Scratchbox. Please take a backup of your files from Scratchbox user home directory if needed.

On Debian based systems, do the following with root permissions:

$ sudo apt-get remove scratchbox-* --purge
$ sudo rm -rf /scratchbox

On non-Debian based systems, you need to stop scratchbox as follows before removing it.

$ sudo /scratchbox/sbin/sbox_ctl stop
$ sudo rm -rf /scratchbox

==Limitations of Scratchbox==

The following limitations have been noted in the usage of Scratchbox:

===VDSO support===

Scratchbox versions [http://lists.scratchbox.org/pipermail/scratchbox-users/2010-June/001618.html prior to 1.0.18 (Hathor)] do not work when VDSO32 support is enabled in the host's kernel, although there are some workarounds for older versions, which are presented here.

If your host has VDSO32 turned on you will get an error like this when trying to login to Scratchbox.

No directory, logging in with HOME=/
Inconsistency detected by ld.so: rtld.c: 1192: dl_main: Assertion `(void *)
ph->p_vaddr == _rtld_local._dl_sysinfo_dso' failed!

===x86-64 kernel===

x86-64 Linux kernels starting from version 2.6.25 enable VDSO32 by default. To temporarily disable VDSO32 execute

sysctl abi.vsyscall32=0

On Linux kernel 2.6.24 <= you can disable VDSO32 by executing

sysctl vm.vdso_enabled=0

or

sysctl kernel.vdso=0

The current setting of VDSO32 can be verified by using sysctl. Only values 0 and 2 are compatible with Scratchbox. In our examples we use 0 (disable). 2 enables compat mode.

You can set all of these permanently by adding the following lines to <code>/etc/sysctl.conf</code>

vm.vdso_enabled = 0
abi.vsyscall32 = 0
kernel.vdso = 0

Save the file and run the command:

$ sudo sysctl -p

Please note the correct line depends on your Linux kernel version. When you execute sysctl -p you may get a warning about unknown keys. You can safely ignore those warnings as long as one of the 3 settings works.

'''WARNING :''' You should try setting these values by echoing them to the given locations before adding them to <code>sysctl.conf</code> to see if they cause any problems. For example, in some Ubuntu Gutsy installations, it has been observed that changing the VDSO settings will hang the system and thus making permanent changes in <code>sysctl.conf</code> may, in these cases, make your system unbootable.

==Known Issues in the SDK==

* A list of issues and their solutions can be found in the [[Developer_FAQ#Maemo_SDK_and_Scratchbox|Developer FAQ]] article
* Unnecessary warnings and debugging messages are printed out when the hildon application framework is started.
* Armel target does not bring up the UI framework
* It has been noted that Xephyr dies with the application framework at times. The crash in question might even be Xephyr related since the application framework behaves differently with different versions/builds of Xephyr. The case seems to be worst on Xephyr that comes with Ubuntu Jaunty, there Xephyr will die when running any application that contains an input field and clicking on that field with a mouse to invoke the input method. On Fedora Core 10 the Xephyr does not mind the mouse clicks but dies when shutting down the application framework. On the other hand Xephyr on Ubuntu Intrepid or even the Intrepid version recompiled for Jaunty does not experience crashing in these situations.<br/>A patch is already available for the Xephyr on Ubuntu Jaunty and can be found at http://bugs.freedesktop.org/show_bug.cgi?id=21591. Binaries packages for [http://launchpadlibrarian.net/30330126/xserver-xephyr_1.6.3-1ubuntu2_i386.deb xserver-xephyr] package and its dependencies ([http://launchpadlibrarian.net/27533744/libgpg-error0_1.6-1ubuntu1_i386.deb libgpg-error0] and [http://launchpadlibrarian.net/28623981/libgcrypt11_1.4.4-2ubuntu2_i386.deb libcrypt11]) can be download from Ubuntu Jaunty repositories.
* The performance of clutter can be improved by enabling hardware acceleration if not enabled already. In some cases, it would require installing restricted/proprietary drivers (Eg: on host machines with ATI or NVidia graphics card). Refer to [[Maemo 5 Clutter performance]] for more details.
* Running Xephyr with <code>-kb</code> option disables entry of “@” symbol. However, removing <code>-kb</code> option disables cursor keys.
* Running Xephyr with <code>-host-cursor</code> is causing Xephyr to crash in Ubuntu Lucid and Debian Squeeze when the Hildon Application Framework is closed.
* Xephyr in Ubuntu Lucid does not support the <code>-kb</code> option anymore. https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/531872
* In order to run ARMEL binaries in scratchbox the <code>mmap_min_address</code> needs to be set to 4096 or lower. Normally the SDK installer warns about that, but in Ubuntu Lucid the /proc entry is visible only to root, so the SDK installer can not see it. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/568844 This also [http://lists.scratchbox.org/pipermail/scratchbox-users/2010-June/001624.html prevents qemu from checking the value], in which case it is assumed to be 0. Because of this, until the bug is fixed (kernel 2.6.34 is unaffected, and at least that version will be in Maverick), the value should be set to 0 on Lucid.
** [http://talk.maemo.org/showpost.php?p=636394&postcount=8 To install on Ubuntu 10.04] (restart installation afterwards):
$ sudo su
$ echo "vm.mmap_min_addr = 0" >> /etc/sysctl.conf
$ sysctl -p
$ exit #to go back to user

[[Category:Scratchbox]]