Difference between revisions of "Repository Layout"

From WebOS-Ports
Jump to navigation Jump to search
(Replaced content with "== Overview == Right layers and branches/revs are always defined in webos-ports-setup/conf/layers.txt. Currently we're using LTS Yocto 3.1 Dunfell release through testing...")
Tag: Replaced
(28 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
== Overview ==
 
== Overview ==
 +
Right layers and branches/revs are always defined in webos-ports-setup/conf/layers.txt. Currently we're using LTS Yocto 3.1 Dunfell release through testing (with LTS Qt 5.15) and Yocto 3.2 Gatesgarth through unstable branch. Next stable build will be with Yocto 3.1 Dunfell as well, once we're ready for new release.
  
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.
+
The stable, testing, unstable branches in webos-ports-setup are rebased on top of Yocto release branch and the only difference is the branch name in the Makefile. That way if you use e.g. testing branch it will automatically switch between Yocto releases once we switch the testing builds on jenkins. Stable is the same as testing most of the time, but has locked meta-webos-ports and meta-smartphone revisions instead of latest.
  
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.
+
Layerman will take care of the checkout of right layers with right revisions - just type make update if you want newer.
 
 
Current (as of right now 27th October 2012) it looks like this:
 
 
 
* bitbake,git://github.com/openembedded/bitbake.git,master,4cd0200e96fb282980a945b80af641a6e022e0b4
 
* openembedded-core,git://github.com/openembedded/oe-core.git,master,40cf43c1c2fa15d0ee4bcc1226d9184747695b88
 
* meta-openembedded,git://github.com/openembedded/meta-oe.git,master,d9b7d6b4cd6b959b3998ddfec9775b64ffa61fe0
 
* meta-smartphone,git://github.com/webOS-ports/meta-smartphone.git,webOS-ports/master,HEAD
 
* meta-webos,git://github.com/webOS-ports/meta-webos.git,webOS-ports/master,HEAD
 
* meta-webos-ports,git://github.com/webOS-ports/meta-webos-ports.git,master,HEAD
 
 
 
* bitbake/oe-core/meta-oe are using master with locked revision (compatible with danny/yocto-v1.3 release).
 
* changes in our meta-webos fork are described here [[MetaWebosCommits]]
 
 
 
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.
 

Revision as of 18:42, 14 September 2020

Overview

Right layers and branches/revs are always defined in webos-ports-setup/conf/layers.txt. Currently we're using LTS Yocto 3.1 Dunfell release through testing (with LTS Qt 5.15) and Yocto 3.2 Gatesgarth through unstable branch. Next stable build will be with Yocto 3.1 Dunfell as well, once we're ready for new release.

The stable, testing, unstable branches in webos-ports-setup are rebased on top of Yocto release branch and the only difference is the branch name in the Makefile. That way if you use e.g. testing branch it will automatically switch between Yocto releases once we switch the testing builds on jenkins. Stable is the same as testing most of the time, but has locked meta-webos-ports and meta-smartphone revisions instead of latest.

Layerman will take care of the checkout of right layers with right revisions - just type make update if you want newer.