[PORT] [ROM] WebOS Port - Build Setup

Search This thread
By:
Advanced…
imfloflo

imfloflo

Senior Member
Apr 20, 2007
3,061
814
Clermont-Ferrand, France
Google Pixel 5
Google Pixel 8
Overview

The following steps will help you to setup a complete build environment for the webos-ports project.
WE DO NOT CURRENTLY SUPPORT webos-image PLEASE BUILD webos-dev-image
Setup the build environment

Code: 
 $ sudo apt-get install gawk         
 $ sudo apt-get install diffstat         
 $ sudo apt-get install chrpath         
 $ sudo apt-get install texinfo (if not on Ubuntu or Debian it will be makinfo instead of texinfo)
 $ cd into-your-build-directory
 $ mkdir webos-ports && cd webos-ports
 $ wget https://raw.github.com/openwebos/build-webos/master/scripts/prerequisites.sh
 $ sudo sh prerequisites.sh
 $ wget https://raw.github.com/webOS-ports/webos-ports-setup/master/Makefile
 $ make setup-webos-ports
Before you can build, you will need some tools. If you try to build without them, bitbake will fail a sanity check and tell you about what's missing, but not really how to get the missing pieces.
This has been tested on Gentoo (shr-chroot) and Ubuntu-12.04 amd64 and should work almost everywhere where valid toolchain is provided.

You need a lot of RAM to link webkit-webos, make sure you have at least 6GB (it's OK when some of that is swap, because it's used only for short part of build).
Webkit needs so much ram to link because it's linking with debug symbols (huge files) which are stripped later in do_package after creating -dbg packages.
You can add extra 2GB of swap file like this:
Code: 
$ dd if=/dev/zero of=swap_2gb.img bs=1024k count=2048
$ mkswap swap_2gb.img
$ sudo swapon swap_2gb.img
If you want it permanently add it to your /etc/fstab.

Building

To configure to build for tuna (notice '.' which is actually bash 'source' command):
Code: 
 $ cd into-your-build-directory/webos-ports/webos-ports
 $ . ./setup-env
To update metadata
Code: 
 $ make update
 # or if it shows warning about different bblayers.conf or layers.txt
 $ make update-conffiles && make update
 # you can also add UPDATE_CONFFILES_ENABLED = 1 to config.mk
 # if you never want to have any uncommited changes in your checkouts RESET_ENABLED = 1 in config.mk
To build the webos-image for the gnex device:
Code: 
$ MACHINE=tuna bb webos-ports-image
 # or for the webos development image
$ MACHINE=tuna bb webos-ports-dev-image
If you get an error about missing qmake-palm, try this:
Code: 
$ MACHINE=tuna bitbake -c cleansstate -f qt4-webos
If you get an error about missing QtWebKit #261, try this:
Code: 
$ MACHINE=tuna bitbake -c cleansstate -f webkit-webos
If you get an error "The BBPATH variable is not set", then you forgot to call:
Code: 
$ . setup-env
After the build completes, you will find your image in <build env>/tmp-eglibc/deploy/images/tuna/
==Speeding up the build==

You can tune bitbake to use more of your processor. Edit webos-ports/conf/local.conf and uncomment the PARALLEL_MAKE and BB_NUMBER_THREADS lines. PARALLEL_MAKE should be set to the number of processor cores you have (or the number you have made available to the VM in the case of a VM) and BB_NUMBER_THREADS can be set from one to two times that, depending upon RAM, processor speed, other tasks running and Hyper-threading support. Example values:

Code: 
PARALLEL_MAKE = "-j 4"
BB_NUMBER_THREADS = "4"
I'm not in charge of this port. This thread is just here to help you, and discuss about this port made by team WEBOS-PORT.
Thanks for their work.

Installing and running the image
Once you have built the image, you'll likely want to install it and run it on your Nexus. See Testing Gnex for further details on that process.
Source and updates : http://webos-ports.org/wiki/Galaxy_Nexus_Build_Setup
 
Last edited:
  • Like
Reactions: mosca_, liuxinyu12322, WEM97 and 29 others
tyraelasd

tyraelasd

Senior Member
Nov 28, 2010
1,445
473
Concepcion
It would be pretty cool to have web os as a port for the Nexus. Wish you all the best

Sent from my Galaxy Nexus using Tapatalk 2
 
B

B1nny

XDA Portal Team / Retired Forum Moderator
May 18, 2008
1,131
850
Nice, I hope webOS will be a succes on our Galaxy Nexuses!

Good luck!
 
B

Bread Pitta

Member
Nov 21, 2008
9
3
Ok, this may be very embarrassing. I was able to follow the process to build the image but I cannot find the image nor how-to flash it on my Nexus. Any help like links, keywords to search for is very appreciated.
 
You must log in or register to reply here.

Similar threads

kaluoshi
  • Locked
[ROM] [4.4.4] [OFFICIAL] ParanoidAndroid 4.6
Replies
41K
Views
8M
M
malybru
Romanbb
  • Locked
[ROM] Android Open Kang Project - maguro - JB
Replies
15K
Views
3M
Mikey
Mikey
bigxie
[ROM] [OTA] [GSM] Android 4.2.2 JDQ39: Rooted Busybox Deodexed/Odexed (2/12/13)
Replies
6K
Views
2M
R
rob_yx
franciscofranco
[KERNEL] [GPL] [GN] franco.Kernel r398
Replies
45K
Views
8M
C
Ctzokas
iceandfire
[ROM] XenonHD-4.4.2 Build 7 (23.05.14) *Truly Stable, Fast & Buttery Smooth*
Replies
7K
Views
2M
A
anirudhbaji

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 32
    imfloflo
    imfloflo
    Overview

    The following steps will help you to setup a complete build environment for the webos-ports project.
    WE DO NOT CURRENTLY SUPPORT webos-image PLEASE BUILD webos-dev-image
    Setup the build environment

    Code: 
     $ sudo apt-get install gawk         
 $ sudo apt-get install diffstat         
 $ sudo apt-get install chrpath         
 $ sudo apt-get install texinfo (if not on Ubuntu or Debian it will be makinfo instead of texinfo)
 $ cd into-your-build-directory
 $ mkdir webos-ports && cd webos-ports
 $ wget https://raw.github.com/openwebos/build-webos/master/scripts/prerequisites.sh
 $ sudo sh prerequisites.sh
 $ wget https://raw.github.com/webOS-ports/webos-ports-setup/master/Makefile
 $ make setup-webos-ports
    Before you can build, you will need some tools. If you try to build without them, bitbake will fail a sanity check and tell you about what's missing, but not really how to get the missing pieces.
    This has been tested on Gentoo (shr-chroot) and Ubuntu-12.04 amd64 and should work almost everywhere where valid toolchain is provided.

    You need a lot of RAM to link webkit-webos, make sure you have at least 6GB (it's OK when some of that is swap, because it's used only for short part of build).
    Webkit needs so much ram to link because it's linking with debug symbols (huge files) which are stripped later in do_package after creating -dbg packages.
    You can add extra 2GB of swap file like this:
    Code: 
    $ dd if=/dev/zero of=swap_2gb.img bs=1024k count=2048
$ mkswap swap_2gb.img
$ sudo swapon swap_2gb.img
    If you want it permanently add it to your /etc/fstab.

    Building

    To configure to build for tuna (notice '.' which is actually bash 'source' command):
    Code: 
     $ cd into-your-build-directory/webos-ports/webos-ports
 $ . ./setup-env
    To update metadata
    Code: 
     $ make update
 # or if it shows warning about different bblayers.conf or layers.txt
 $ make update-conffiles && make update
 # you can also add UPDATE_CONFFILES_ENABLED = 1 to config.mk
 # if you never want to have any uncommited changes in your checkouts RESET_ENABLED = 1 in config.mk
    To build the webos-image for the gnex device:
    Code: 
    $ MACHINE=tuna bb webos-ports-image
 # or for the webos development image
$ MACHINE=tuna bb webos-ports-dev-image
    If you get an error about missing qmake-palm, try this:
    Code: 
    $ MACHINE=tuna bitbake -c cleansstate -f qt4-webos
    If you get an error about missing QtWebKit #261, try this:
    Code: 
    $ MACHINE=tuna bitbake -c cleansstate -f webkit-webos
    If you get an error "The BBPATH variable is not set", then you forgot to call:
    Code: 
    $ . setup-env
    After the build completes, you will find your image in <build env>/tmp-eglibc/deploy/images/tuna/
    ==Speeding up the build==

    You can tune bitbake to use more of your processor. Edit webos-ports/conf/local.conf and uncomment the PARALLEL_MAKE and BB_NUMBER_THREADS lines. PARALLEL_MAKE should be set to the number of processor cores you have (or the number you have made available to the VM in the case of a VM) and BB_NUMBER_THREADS can be set from one to two times that, depending upon RAM, processor speed, other tasks running and Hyper-threading support. Example values:

    Code: 
    PARALLEL_MAKE = "-j 4"
BB_NUMBER_THREADS = "4"
    I'm not in charge of this port. This thread is just here to help you, and discuss about this port made by team WEBOS-PORT.
    Thanks for their work.

    Installing and running the image
    Once you have built the image, you'll likely want to install it and run it on your Nexus. See Testing Gnex for further details on that process.
    Source and updates : http://webos-ports.org/wiki/Galaxy_Nexus_Build_Setup
    View
    14
    Raphi86
    Raphi86
    New Screens:
    Sysmenu.png

    Lockscreen.png

    Keyboard.png

    Homescreen.png

    Cardview.png


    Source: http://webos-ports.org/wiki/Galaxy_Nexus
    View
    10
    imfloflo
    imfloflo
    Videos



    Pictures


    More Pictures : http://webos-ports.org/wiki/Galaxy_Nexus
    View
    4
    F
    fil286n
    byt3b0mb said:
    are the build images available anywhere for download? i dont know if everyone has the necessary hardware to build from source, and personally i would just like to give the alpha build a flash and test.
    Click to expand...
    Click to collapse

    I found a directory here. http://build.webos-ports.org/webos-ports/images/tuna/
    It have some build of Open WebOS for Tuna with last update is
    webos-dev-image-tuna.ext4 18-Dec-2012 19:13 485210112
    :cool:
    Try it if u want.
    View
    2
    MadCobbler
    MadCobbler
    Thanks for this, just having a go at this now ;)

    Edit: Damn it seems it doesn't like Ubuntu 10.10

    Suppose I needed an excuse to update........
    View

New posts