The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)

Nemo/OBS

From Mer Wiki
< Nemo(Difference between revisions)
Jump to: navigation, search
(link to Osc_setup wiki page added to "getting started")
(Rewritten for new structure)
Line 1: Line 1:
 
= Getting started with the build system =
 
= 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.
−
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
 
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
 
   apiurl = https://api.opensuse.org
−
 
 
to
 
to
−
 
 
   apiurl = https://api.pub.meego.com
 
   apiurl = https://api.pub.meego.com
  
 
Alternatively you can follow the more detailed instructions here: [[Osc_Setup]]
 
Alternatively you can follow the more detailed instructions here: [[Osc_Setup]]
−
 
 
Further down in the same file you will find a config section named <code><nowiki>[https://api.opensuse.org]</nowiki></code>. Change the section name to <code><nowiki>[https://api.pub.meego.com]</nowiki></code>, and set the corresponding <code>user =</code> and <code>pass =</code> config options to match your MeeGo account.
 
Further down in the same file you will find a config section named <code><nowiki>[https://api.opensuse.org]</nowiki></code>. Change the section name to <code><nowiki>[https://api.pub.meego.com]</nowiki></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
 
You can test your <code>osc</code> set-up by issuing
−
 
 
   osc ll
 
   osc ll
−
 
 
which should produce a list of all projects on the MeeGo build server.
 
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].
 
A more comprehensive "OBS getting started" page is at the [http://wiki.meego.com/Getting_started_with_OBS MeeGo wiki].
  
−
= Nemo OBS structure =
+
= Nemo Mobile OBS project structure =
−
 
+
OBS: https://build.pub.meego.com/ , new OBS at https://build.merproject.org/
−
OBS: https://build.pub.meego.com/
+
  
 
Maintainer: Sage, #nemomobile @ Freenode
 
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. These repositories are identified with latest_<arch> and next_<arch>, where <arch> is the architecture the repository is compiling against.
  
−
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).
+
All the nemo related project are under the '''nemo''' project, and they follow the following structure:
  
−
== CE:Adaptation:N900 ==
+
nemo:<phase>:<project>:<subproject>
−
'''Compiled against:''' Mer Core
+
  
−
Nokia N900 Hardware adaptation project
+
<phase> is stable, testing or devel
  
−
== CE:Adaptation:N950-N9 ==
+
* each <phase> has a complete nemo tree below it and is self-contained (ie no building against projects in a different <phase>)
−
'''Compiled against:''' Mer Core
+
* when a package is QA'ed it moves (how?) to the next phase, in order of devel -> testing -> stable
 +
* the process from developer point of view starts from 'devel' phase where the changes are submitted, after this it is responsibility of maintainer(s) and QA team(s) to forward the new submission forward and report back on any issues.
  
−
Nokia N950 and N9 Hardware adaptation project
+
The subprojects are described below.
  
−
== CE:Adaptation:N9xx-common ==
+
== nemo:<phase>:mw ==
−
'''Compiled against:''' Mer Core
+
'''Compiled against:''' mer:mds:core:{latest,next}:{arch}/{latest,next}_{arch}
  
−
Common parts for Nokia N900, N950 and N9 hardware adaptations
+
'''Architectures (schedulers)''': i486 (i586), i586, armv6el (armv7el), armv7hl (armv8el), armv7tnhl (armv8el?)
  
−
== CE:Adaptation:PandaBoard ==
+
Shared components between ux and apps
−
'''Compiled against:''' Mer Core
+
  
−
Pandaboard OMAP4 hardware adaptation project
+
Contains:
 +
* policyframework
 +
* maliit
 +
* qt-components
 +
* telepathy
  
−
== CE:Adaptation:x86-generic ==
+
== nemo:<phase>:ux ==
−
'''Compiled against:''' Mer Core
+
'''Compiled against:''' CE:MW:MTF
  
−
Generic x86 architecture adaptation project
+
'''Architectures (schedulers)''': i486 (i586), i586, armv6el (armv7el), armv7hl (armv8el), armv7tnhl (armv8el?)
  
−
== CE:Apps ==
+
lipstick based UX for Nemo
−
'''Compiled against:''' CE:MW:Shared
+
  
−
Project for Applications in Nemo that are compiled against CE:MW:Shared.
+
== nemo:<phase>:apps ==
 +
'''Compiled against:''' nemo:<phase>:mw
  
−
== CE:Apps:MTF ==
+
'''Architectures (schedulers)''': i486 (i586), i586, armv6el (armv7el), armv7hl (armv8el), armv7tnhl (armv8el?)
−
'''Compiled against:''' CE:MW:MTF
+
  
−
Project for MeeGo Touch Framework based Applciations in Nemo that are compiled against the CE:MW:MTF.
+
Project for applications in Nemo, such as calculator, contacts, messaging etc.
  
−
== CE:MW:MTF ==
+
== nemo:<phase>:hw:* ==
−
'''Compiled against:''' CE:MW:Shared
+
All the hardware apdations are compiled against nemo:<phase>:mw if not mentioned otherwise.
−
'''Development Project:''' Project:MTF:MW
+
  
−
MTF middleware project that contains packages that are generally needed to create MTF based applications.
+
=== nemo:<phase>:hw:n9xx-common ===
 +
Common parts for Nokia N900, N950 and N9 hardware adaptations
  
−
== CE:MW:PlasmaActive ==
+
Architectures: armv7hl
−
'''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.
+
=== nemo:<phase>:hw:n900 ===
 +
Compiles against nemo:<phase>:hw:n9xx-common
  
−
== CE:MW:Shared ==
+
Architectures: armv7hl
−
'''Compiled against:''' Mer Core
+
  
−
Shared components for different UX's and Apps.
+
Nokia N900 Hardware adaptation project
  
−
Contains:
+
=== nemo:<phase>:hw:n950-n9 ===
−
* policyframework
+
Compies against nemo:<phase>:hw:n9xx-common
−
* maliit
+
  
−
== CE:Utils ==
+
Architectures: armv7hl
−
'''Compiled against:''' Mer Core
+
  
−
Some generic utilities that are not part of Mer Core but are considered useful in generic development.
+
Nokia N950 and N9 Hardware adaptation project
  
−
Contains e.g.,: iotop, lynx, screen, wget
+
=== nemo:<phase>:hw:pandaboard ===
 +
Architectures: armv7hl
  
−
== CE:UX:lipstick ==
+
PandaBoard OMAP4 hardware adaptation project
−
'''Compiled against:''' ???
+
  
−
WIP
+
=== nemo:<phase>:hw:x86-generic ===
 +
Architectures: i586, i486
  
−
== CE:UX:MTF ==
+
Generic x86 architecture adaptation project
−
'''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.
+

Revision as of 13:32, 6 September 2012

Contents

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

Alternatively you can follow the more detailed instructions here: Osc_Setup Further down in the same file you will find a config section named [https://api.opensuse.org]. Change the section name to [https://api.pub.meego.com], 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.

Nemo Mobile OBS project structure

OBS: https://build.pub.meego.com/ , new OBS at https://build.merproject.org/

Maintainer: Sage, #nemomobile @ Freenode

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. These repositories are identified with latest_<arch> and next_<arch>, where <arch> is the architecture the repository is compiling against.

All the nemo related project are under the nemo project, and they follow the following structure: 

nemo:<phase>:<project>:<subproject>

<phase> is stable, testing or devel

  • each <phase> has a complete nemo tree below it and is self-contained (ie no building against projects in a different <phase>)
  • when a package is QA'ed it moves (how?) to the next phase, in order of devel -> testing -> stable
  • the process from developer point of view starts from 'devel' phase where the changes are submitted, after this it is responsibility of maintainer(s) and QA team(s) to forward the new submission forward and report back on any issues.

The subprojects are described below.

nemo:<phase>:mw

Compiled against: mer:mds:core:{latest,next}:{arch}/{latest,next}_{arch}

Architectures (schedulers): i486 (i586), i586, armv6el (armv7el), armv7hl (armv8el), armv7tnhl (armv8el?)

Shared components between ux and apps

Contains:

  • policyframework
  • maliit
  • qt-components
  • telepathy

nemo:<phase>:ux

Compiled against: CE:MW:MTF

Architectures (schedulers): i486 (i586), i586, armv6el (armv7el), armv7hl (armv8el), armv7tnhl (armv8el?)

lipstick based UX for Nemo

nemo:<phase>:apps

Compiled against: nemo:<phase>:mw

Architectures (schedulers): i486 (i586), i586, armv6el (armv7el), armv7hl (armv8el), armv7tnhl (armv8el?)

Project for applications in Nemo, such as calculator, contacts, messaging etc.

nemo:<phase>:hw:*

All the hardware apdations are compiled against nemo:<phase>:mw if not mentioned otherwise.

nemo:<phase>:hw:n9xx-common

Common parts for Nokia N900, N950 and N9 hardware adaptations

Architectures: armv7hl

nemo:<phase>:hw:n900

Compiles against nemo:<phase>:hw:n9xx-common

Architectures: armv7hl

Nokia N900 Hardware adaptation project

nemo:<phase>:hw:n950-n9

Compies against nemo:<phase>:hw:n9xx-common

Architectures: armv7hl

Nokia N950 and N9 Hardware adaptation project

nemo:<phase>:hw:pandaboard

Architectures: armv7hl

PandaBoard OMAP4 hardware adaptation project

nemo:<phase>:hw:x86-generic

Architectures: i586, i486

Generic x86 architecture adaptation project

Retrieved from "https://wiki.merproject.org/wiki/index.php?title=Nemo/OBS&oldid=2395"
Personal tools