Editing Mer/Build

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
-
{{Mer}}
+
=Buiding Mer.=
-
This section documents how to use the [http://build.opensuse.org openSUSE Build Service] with Mer. More on the openSUSE Buildservice [http://en.opensuse.org/Build_Service here].
+
This page is a collection of ramblings about the ongoing experiment with OBS
-
A simple way to think of OBS is as a version control system for source tarballs and .dsc files and whenever you commit a tarball the build farm compiles it for you.
+
https://build.opensuse.org
-
Over and above this OBS provides a local tool called osc that lets you do clean builds not only for your own OS and architecture but also for other distros and even other architectures (armel).
+
Mer is based on Ubuntu Jaunty
 +
  http://cdimage.ubuntu.com/releases/jaunty/alpha-6/
-
==Getting Started==
+
== Installing OBS tools locally ==
 +
You'll need an account with Novell : http://is.gd/nzxP
-
Approaching OBS can look overwhelming... but it is perfectly possible to get an existing package built for Mer just using a web browser.
+
Assuming a debian or ubuntu development box locally:
-
The first thing to do is to [[/Install OBS|install OBS]]. This will provide access to the tools and source used to build Mer.
+
Add osc repo top apt.
 +
  deb http://download.opensuse.org/repositories/openSUSE:/Tools/xUbuntu_8.10/ /
 +
or
 +
  deb http://download.opensuse.org/repositories/openSUSE:/Tools/Debian_5.0/ /
 +
to
 +
  /etc/apt/sources.list.d/obs.list
-
Then you should become familiar with building an application using OBS but outside the Mer repository. This is explained in detail in [[/Application Building|Application Building]] which takes you through an example application.
+
Then
 +
  apt-get update
 +
  apt-get install osc
 +
run
 +
  osc
 +
and enter novell.com username/passwd
-
==Mer Internals==
+
Go and login to https://build.opensuse.org
-
When you are comfortable building your own applications for Mer then you can look at the [[Mer/Packages|Mer Packages]] and start helping to improve Mer itself.
+
Make sure you click the "let me build packages" button.
-
There are [[/Processes|processes]] used to manage the Mer packages which may include [[/UsingGitorious|Using Gitorious]].
+
There is a link to 'Home Project' on the left I think. Follow this and enter a description.
-
The OBS [[/Cross Build|cross build]] page describes how the OBS has been accelerated.
+
From now on where I use "home:lbt" uses your own "home:username"
-
== OBS Build Farm ==
+
Now:
 +
  osc ls home:lbt
 +
will list
-
http://wiki.maemo.org/Mer/Documentation/Build/Common_Problems
+
  osc co home:lbt
 +
will checkout the project
 +
now
 +
  osc meta pkg -e home:lbt epeg
-
== QEMU armel image ==
+
edit the name/description
 +
run
 +
  osc up
 +
This makes a package dir
 +
  cp package.tar.gz package.dsc homt:lbt/package
 +
  cd package
 +
Then add them to version control
 +
  osc addremove
 +
and upload them
 +
  osc ci
-
An Ubuntu armel image for QEMU is available from here:<br>
+
Now we need to pick build targets:
-
http://gitorious.org/mer-toggles/qemu-armel-image (login: qemu/qemu)
+
  https://build.opensuse.org/project/add_target_simple?project=home:lbt
-
<br>
+
And pick one or two ( I picked Debian Lenny and Ubuntu 8.10)
-
Based on these instructions:<br>
+
-
https://wiki.ubuntu.com/ARM/RootfsFromScratch<br>
+
-
This is NOT a Mer development image like Mer VMDK is.
+
To watch what is going on:
 +
  osc buildlog <target>
 +
so
 +
  osc buildlog Debian_5.0 i586
-
== Mer Source ==
+
This does something like a "tail -f" of the Xen builder.
-
Currently you cannot <code>apt-get source</code> for Mer.
+
=== Standalone Project ===
-
Our approach requires you to get a Novell account and is similar to the one in HHGTTG:
+
This creates a standalone project and builds against another project
-
<blockquote>
+
On the web, create the (sub)project maemopad.
-
"`...You hadn't exactly gone out of your way to call attention to them had you? I mean like actually telling anyone or anything.'<br>
+
-
`But the plans were on display...'<br>
+
-
`On display? I eventually had to go down to the cellar to find them.'<br>
+
-
`That's the display department.'<br>
+
-
`With a torch.'<br>
+
-
`Ah, well the lights had probably gone.'<br>
+
-
`So had the stairs.'<br>
+
-
`But look you found the notice didn't you?'<br>
+
-
`Yes,' said Arthur, `yes I did. It was on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying "Beware of The Leopard".'"
+
-
</blockquote>
+
-
<br>
+
-
But slightly simpler...
+
-
Nb... the fix is trivial and simply requires you to modify the GPL licensed OBS system to publish debian style source distros ... patches accepted.
+
In the repository section add a repository and from advanced select the Mer project: home:lbt:Mer:010
 +
 
 +
Goto your obs base (eg /scratch3/maemo/Mer/obs) and checkout the project:
 +
  osc co home:lbt:maemopad
 +
 
 +
Now create the package metadata:
 +
  osc meta pkg -e home:lbt:maemopad maemopad
 +
 
 +
and get a local copy (empty still):
 +
  cd home:lbt:maemopad/
 +
  osc up
 +
 
 +
the 'osc up' created a directory so go into it and get the source:
 +
  cd maemopad/
 +
  wget http://repository.maemo.org/pool/maemo4.1.2/free/m/maemopad/maemopad_2.4.dsc
 +
  wget http://repository.maemo.org/pool/maemo4.1.2/free/m/maemopad/maemopad_2.4.tar.gz
 +
 
 +
Use the cheap'n'cheerful 'register all file adds and removes with vc'-command:
 +
  osc addremove
 +
 
 +
and then commit the source which uploads it to the OBS
 +
  osc commit -m "added source"
 +
 
 +
This will trigger a rebuild and you can access the logs.
 +
 
 +
 
 +
=== Linking ===
 +
 
 +
To link to a source create a _link file containing:
 +
  <link project="linked project name" package="linked package name">
 +
 
 +
optionally:
 +
  <patches>
 +
    <apply name="name of the first patch" />
 +
  </patches>
 +
 
 +
Sadly these patches apply to the files in the source; so this means you need to apply the diff to the maemo-ised diff file.
 +
 
 +
== Scenarios ==
 +
 
 +
In the following, Mer environment is defined as the sum of packages with Ubuntu packages, with Mer repository overlaid on top, not what is built in a 'Mer' project.
 +
 
 +
1. A lone developer sits down and decides to create a project. He assigns a package name to this and his name as maintainer. He builds it locally for Mer and tries it out as he develops it through dpkg-buildpackage'ing (or osc build?) locally and testing his package. He finishes his release, and dpkg-buildpackage -S -us -uc, generating a .dsc and tar.gz. He would like to build his package for the Mer environment, the X86 and ARMEL targets. He doesn't want to maintain a local toolchain beyond his x86 VMDK, so he submits the build job to the OpenSUSE Build Service (which he has registered with). He can then observe the build progress and he can subsequently download resulting .deb(s) and .changes file to upload to the Mer (Extras) repository.
 +
 
 +
2. Variation on the first but with OpenSUSE Build Service located on maemo.org
 +
 
 +
3. A company developer sits down and creates a project. He takes this source from a company source code repository, assigns a package name and setting his name as maintainer. He builds it locally for Mer and tries it out as he develops it through dpkg-buildpackage'ing (or osc build?) locally and testing his package. He generates a release (generating a .dsc and tar.gz) and he would like to target Mer environment, and Ubuntu, the X86 and ARMEL targets. He would like to build locally on his VMDK, as the source code should never leave the company premises. He can then watch the build progress and subsequently gets the resulting .deb(s) and .changes, to be able to upload. He should not need a login at all to build locally
 +
 
 +
4. Same as 3, but is okay to need a login, it is assumed there is a OBS Server appliance with build workers in the company.
 +
 
 +
== Naming and Deltas ==
 +
 
 +
Mer is derived from Ubuntu with the intial releases being based on Jaunty.
 +
 
 +
This means that in general you get Ubuntu packages.
 +
 
 +
In OBS terms, Mer builds against Ubuntu Jaunty (ie build-dependencies are met from Jaunty)
 +
 
 +
However, Maemo provides some excellent libraries, UIs and applications that Mer will use.
 +
 
 +
So Mer is "linked to" the OBS Maemo project (which just contains an upload of the Maemo source)
 +
 
 +
 
 +
 
 +
mer=orig+delta(deb)+delta(maemo)+delta(mer)      mer!=orig+delta(deb+maemo+mer)

Learn more about Contributing to the wiki.


Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!


Cancel | Editing help (opens in new window)

Templates used on this page:

Retrieved from "http://wiki.maemo.org/Mer/Build"