(→Harmattan) |
(→OBS local build) |
||
| Line 126: | Line 126: | ||
<pre> | <pre> | ||
osc build MeeGo_1.2_Harmattan_Maemo.org_MeeGo_1.2_Harmattan_standard armv7el | osc build MeeGo_1.2_Harmattan_Maemo.org_MeeGo_1.2_Harmattan_standard armv7el | ||
| + | </pre> | ||
| + | |||
| + | ====Possible pitfalls==== | ||
| + | '''Problem:''' | ||
| + | <pre> | ||
| + | failed to run command `/sbin/ldconfig': No such file or directory | ||
| + | </pre> | ||
| + | and | ||
| + | <pre> | ||
| + | chroot: failed to run command `dpkg': No such file or directory | ||
| + | </pre> | ||
| + | '''Solution:''' | ||
| + | Install more Qemu related packages. :) Eq. on Ubuntu 11.04 this helps: | ||
| + | <pre> | ||
| + | sudo apt-get install qemu* | ||
</pre> | </pre> | ||
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!
Contents |
apt-get install osc may 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.
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. mypkg_1.0.0.tar.gz, mypkg_1.0.0.dsc, mypkg_1.0.0.debian.tar.gz)
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 debian/rules):
# Uncomment this line for use without Qt Creator.
clean section, comment the line $(MAKE) clean
Second, to get the files needed for building you may add a custom build step:
C:\QtSDK\Madde\wbin\mad.cmd
%{buildDir}
-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>.tar.gz and <packagename>-<version>.dsc (together with a non-needed <packagename>-<version>.source.changes) in the directory above the source directory.
Take care:
QtCreator uses the debian directory for packaging. However, it only copies the content of qtc_packaging/debian_harmattan into 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 debian before.
Security framework relevant applications:
The 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 dependencies in the control file are aegis-builder (>= 1.6), aegis-manifest-dev.
osc -A https://api.pub.meego.com co home:[username]
osc add [filename]
osc commit
At this point the OBS will try to build your project remotely. You can also build locally by doing osc build
If you add new packages later on or commit changes from another computer you can update your local copy by doing
osc update
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.
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.
osc co home:name:project
cd /home:name:project/package
osc build
osc build MeeGo_1.2_Harmattan_Maemo.org_MeeGo_1.2_Harmattan_standard armv7el
Problem:
failed to run command `/sbin/ldconfig': No such file or directory
and
chroot: failed to run command `dpkg': No such file or directory
Solution: Install more Qemu related packages. :) Eq. on Ubuntu 11.04 this helps:
sudo apt-get install qemu*
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 deb and 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
Enable Extras-devel.