Repository Layout

From WebOS-Ports
Revision as of 22:32, 3 October 2012 by Scoutcamper (talk | contribs) (Created page with "== Overview == Right layers and branches/revs are always defined in webos-ports/webos/layers.txt and mcf is calling simplified oebb.sh (+layerman) script to checkout/update them...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Overview

Right layers and branches/revs are always defined in webos-ports/webos/layers.txt and mcf is calling simplified oebb.sh (+layerman) script to checkout/update them.

We're using mcf but in simplified form too, it does not use git submodules, but normal checkouts (managed by layerman). And we've removed options to enable/disable layers (one setup to rule them all). I would also change build layout, because separate BUILD-machine dir is not needed and one tmpdir is more effective - sharing native and cross builds. Each machine has separate sysroot in it so no problem with this.

Current (as of right now 3rd October 2012) it looks like this:

  • bitbake/oe-core/meta-oe are using master with locked revision (from 2012-08-18).
  • meta-smartphone is using master/HEAD, but because master should stay compatible with oe-core/meta-oe HEAD we plan to create webos-ports/master branch there as soon as we have some commits in master which needs newer oe-core or meta-oe then what we have in webos setup.
  • meta-webos, meta-webos-ports are using HEAD and need valid user to checkout from github, jenkins setups should get own github account.

There are currently the following repositories needed to build webos-ports:

  • openembedded-core
  • meta-openembedded/meta-oe
  • meta-webos
    • The layer from the Open webOS project
  • meta-webos-ports
    • Layer with additions for meta-webos needed for webos-ports
  • meta-smartphone/meta-samsung
    • Hardware support for the gnex device
  • meta-smartphone/meta-fso
  • meta-smartphone/meta-android

Each of this will have a webos-ports/master branch if there are additional commits which are not upstream yet. If there is no webos-ports/master branch the master branch should be used. The master branch will always track the upstream master branch!

Layer description

meta-webos

This layers contains the recipes needed for openwebos. This is the original repository from the openwebos project with some additional changes which should go upstream in the near future.

meta-webos-ports

This layer contains several additions to meta-webos which can not go into meta-webos as they are specific for the webos-ports project.