m (remove leading / from path)
|Line 133:||Line 133:|
* enter a package folder folder
* enter a package folder folder
* initiate local build
* initiate local build
The MeeGo Open Build System (OBS) seems rather complicated, this page will attempt to make it nice and easy to get started. See also the Mer project's documentation on application building with OBS.
It's a work in progress, feel free to add and modify!
apt-get install oscmay work out-of-the-box on recent versions of Ubuntu & Debian, other repositories are available on openSUSE tools)
OBS is based around projects, packages and repositories. Packages have a set of files (source code, packaging meta-data, etc.) which are compiled by build servers against particular distributions. Each distribution results in your code being available in a repository.
Your home project is like a home directory in which you can create sub-projects, repositories, etc.
A project is required before anything can be built.
A sub-project allows you to group related activities together.
As Harmattan OBS support is still in development, you can add it through the advanced interface.
Before trying to issue submit requests to projects that are under automated integration (ex. CE:* projects on community OBS), make sure you have created the correct set of repositories needed.
For each repository in target project, there should be a repository in source project which builds only against the target repository and have at least the same architectures as the target repository they build against.
This can be done easily using the addrepos osc plugin , drop it in your ~/.osc-plugins and run the command :
osc -A https://api.pub.meego.com addrepos MYPROJECT TARGETPROJECT
It will open an editor with the repositories appended to the bottom of your prj meta.
For MeeGo you need a .spec file and a tarball containing your source code, etc.
For Harmattan you need a
.dsc file, source tarball and
.debian.tar.gz (this allows one to keep the debian directory out of the source). The source is extracted using
dpkg-source -x ....dsc, so restrictions on file formats apply (e.g.
Alternatively, you may just use the
.dsc together with a
.tar.gz file containing both, the sources and the debian directory.
The steps below are encapsulated in a follow-up to mud-builder, called
mud2. The tool only has a dependency on Perl and performs all the steps below, hoping to streamline the process of taking Qt Creator projects and producing MeeGo, Harmattan and Fremantle OBS-compatible files.
First, you need to modify the rules file (
qtc_packaging/debian_harmattan/rules, which is then copied to
# Uncomment this line for use without Qt Creator.
cleansection, comment the line
Second, to get the files needed for building you may add a custom build step:
C:\QtSDK\Madde\wbin\mad.cmdor in Linux use
-t harmattan-platform-api dpkg-buildpackage -sa -S -uc -us -Imoc -Iobj -Ircc -Iui -I.svn -I*.deb -I*.changes -Iqtc_packaging -IMakefile -I*.pro.user -I<packagename>
Notice that most of the command arguments remove unneccessary files from the tar package. They are not mandatory but reduce file size.
You will get the resulting
<packagename>-<version>.dsc (together with a non-needed
<packagename>-<version>.source.changes) in the directory above the source directory.
QtCreator uses the
debian directory for packaging. However, it only copies the content of
debian when you deploy the package (thus press run or debug). If you change something in
qtc_packaging/debian_harmattan and only run a build without run/debug, you must manually copy the changes to
Security framework relevant applications:
rules file must include a step to add the
<package name>.aegis manifest into the built debian archive. For this, add
aegis-deb-add -control debian/<package name>/DEBIAN/control .. debian/<package name>.aegis=_aegis at the end (after
dh_builddeb). Needed build dependency in the
control file is
aegis-builder (>= 1.6).
If you are using Windows or having build problems with changelog or rules file:
It seams that QTCreator for Windows sometimes creates the changelog and rules file with windows lineendings.
Which causes the OBS to fail. (a
rules file with wrong lineendings causes the
clean step to fail.
osc -A https://api.pub.meego.com co home:[username]
osc add [filename]
At this point the OBS will try to build your project remotely. You can also build locally by doing
If you add new packages later on or commit changes from another computer you can update your local copy by doing
What to do if packages don't build in OBS.
It is advised to first try if a package builds in the Scratchbox based SDK before submitting it to OBS. The Scratchbox environment should be reasonably similar to OBS and lower rebuild time enables faster debugging of packaging issues.
Also, some packages from recent distributions might complain about out of date build dependencies, mostly concerning debhelper and cdbs. As debhelper and cdb are generally not easy to replace with newer versions, it is possible to either use older packages or edit the debian/control and debian/control.in and downgrade the dependencies.
It is possible to build packages locally, using the osc tool. Also unlike during the online build, it is possible to enter the build chroot and inspect its state. Also, local builds do not need to wait in the online build queue and may be faster (depending on local hardware).
osc co home:name:project
osc build MeeGo_1.2_Harmattan_Maemo.org_MeeGo_1.2_Harmattan_standard armv7el
Problem: Harmattan packages might fail to download (404) during a local build.
Solution: Just wait, after all of the packages have failed it will use an alternate download method that will work.
failed to run command `/sbin/ldconfig': No such file or directory
chroot: failed to run command `dpkg': No such file or directory
Solution:There are some Qemu packages missing in you system (most probably qemu-user-static or an equivalent).
On Ubuntu 11.04, these packages should be installed:
qemu-user-static qemu-common qemu-kvm qemu
NOTE: Looks like even just qemu-user-static package suffices for builds to run to completion.
Main article: Zypper#Adding_a_repository
zypper ar -f http://repo.pub.meego.com/home:/username/repository/ title zypper in <package>
/etc/apt/sources.list.d/project.list(where project is a memorable name, e.g. your username for your home project), containing the download link, prefixed with
deband suffixed by
./. For example:
deb http://repo.pub.meego.com/home:/jaffa/Harmattan/ ./
apt-get update apt-get install package
Updates to the installed applications will appear at Settings > Applications > Manage Applications > Updates