Revision as of 18:59, 24 June 2012 (view source) Iamer (Talk | contribs) (→‎Nemo OBS structure) ← Older edit		Revision as of 12:32, 17 August 2012 (view source) Thilo (Talk | contribs) (Added instructions on how to set up an OBS account and platform sdk osc configuration.) Newer edit →
Line 86:		Line 86:
	Plasma Active UX components.		Plasma Active UX components.
		+
		+
		+	= Getting started with the build system =
		+
		+	To get started you will need to [https://build.pub.meego.com/user/register_user activate your MeeGo account for OBS]. Upon initial login you will be guided through a mini-process to set up your home repository.
		+
		+	After this it's a good idea to set up <code>osc</code> in the [https://wiki.merproject.org/wiki/Platform_SDK Mer Platform SDK] with the new account. <code>osc</code> is a command line front-end for the build service. When issuing <code>osc help</code> for the first time you will be guided through a mini-process to set up a local default configuration. After the initial set-up completed just fire up your favorite editor and open the file <code>~/.oscrc</code>. In the file, change
		+
		+	apiurl = https://api.opensuse.org
		+
		+	to
		+
		+	apiurl = https://api.pub.meego.com
		+
		+
		+	Further down in the same file you will find a config section named <code>[https://api.opensuse.org]</code>. Change the section name to <code>[https://api.pub.meego.com]</code>, and set the corresponding <code>user =</code> and <code>pass =</code> config options to match your MeeGo account.
		+
		+	You can test your <code>osc</code> set-up by issuing
		+
		+	osc ll
		+
		+	which should produce a list of all projects on the MeeGo build server.
		+
		+	A more comprehensive "OBS getting started" page is at the [http://wiki.meego.com/Getting_started_with_OBS MeeGo wiki].

---

Revision as of 12:32, 17 August 2012

Contents 1 Nemo OBS structure 1.1 CE:Adaptation:N900 1.2 CE:Adaptation:N950-N9 1.3 CE:Adaptation:N9xx-common 1.4 CE:Adaptation:PandaBoard 1.5 CE:Adaptation:x86-generic 1.6 CE:Apps 1.7 CE:Apps:MTF 1.8 CE:MW:MTF 1.9 CE:MW:PlasmaActive 1.10 CE:MW:Shared 1.11 CE:Utils 1.12 CE:UX:lipstick 1.13 CE:UX:MTF 1.14 CE:UX:PlasmaActive 2 Getting started with the build system

Nemo OBS structure

OBS: https://build.pub.meego.com/

Maintainer: Sage, #nemomobile @ Freenode

http://sage.kapsi.fi/Mer/misc/Nemomobile-OBS-project-structure-draft.png

In each project there are two sets of repositories. One repository chain that builds against current release of Mer Core and another that builds against the "next" prerelease of Mer Core (identifiable by "Mer_Core-next" in their name).

CE:Adaptation:N900

Compiled against: Mer Core

Nokia N900 Hardware adaptation project

CE:Adaptation:N950-N9

Compiled against: Mer Core

Nokia N950 and N9 Hardware adaptation project

CE:Adaptation:N9xx-common

Compiled against: Mer Core

Common parts for Nokia N900, N950 and N9 hardware adaptations

CE:Adaptation:PandaBoard

Compiled against: Mer Core

Pandaboard OMAP4 hardware adaptation project

CE:Adaptation:x86-generic

Compiled against: Mer Core

Generic x86 architecture adaptation project

CE:Apps

Compiled against: CE:MW:Shared

Project for Applications in Nemo that are compiled against CE:MW:Shared.

CE:Apps:MTF

Compiled against: CE:MW:MTF

Project for MeeGo Touch Framework based Applciations in Nemo that are compiled against the CE:MW:MTF.

CE:MW:MTF

Compiled against: CE:MW:Shared Development Project: Project:MTF:MW

MTF middleware project that contains packages that are generally needed to create MTF based applications.

CE:MW:PlasmaActive

Compiled against: CE:MW:Shared

Middleware project for Plasma Active that contains packages that are not included in CE:MW:Shared, and are not part of the PlasmaActive UX but are still required for the Plasma Active UX to work.

CE:MW:Shared

Compiled against: Mer Core

Shared components for different UX's and Apps.

Contains:

• policyframework
• maliit

CE:Utils

Compiled against: Mer Core

Some generic utilities that are not part of Mer Core but are considered useful in generic development.

Contains e.g.,: iotop, lynx, screen, wget

CE:UX:lipstick

Compiled against: ???

WIP

CE:UX:MTF

Compiled against: CE:MW:MTF Development Project: Project:MTF:UX

MeeGo Touch Framework based UX

CE:UX:PlasmaActive

Compiled against: CE:MW:PlasmaActive

Plasma Active UX components.

Getting started with the build system

To get started you will need to activate your MeeGo account for OBS. Upon initial login you will be guided through a mini-process to set up your home repository.

After this it's a good idea to set up osc in the Mer Platform SDK with the new account. osc is a command line front-end for the build service. When issuing osc help for the first time you will be guided through a mini-process to set up a local default configuration. After the initial set-up completed just fire up your favorite editor and open the file ~/.oscrc. In the file, change

 apiurl = https://api.opensuse.org

to

 apiurl = https://api.pub.meego.com

Further down in the same file you will find a config section named [1]. Change the section name to [2], and set the corresponding user = and pass = config options to match your MeeGo account.

You can test your osc set-up by issuing

 osc ll

which should produce a list of all projects on the MeeGo build server.

A more comprehensive "OBS getting started" page is at the MeeGo wiki.