WebOS Internals - User contributions [en]

Accessing Linux Debian

2011-07-01T18:24:15Z

Loudergood: typo fix

Though the Ubuntu packages that Palm distributes will install on most linux systems, unless you have converted your Debian system to use the upstart daemon novacomd will not start automatically when your computer does. This can be fixed quite easily by installing a sysv style init script and adding it to the boot process.

These steps must be run as root

1. Download the palm-novacom package for your system (only tested with the 32bit package so far)

2. Switch to root and install the package

3. Save this script as /etc/init.d/novacomd and be very careful to not touch any other files in this directory

<pre>
#! /bin/sh
### BEGIN INIT INFO
# Provides: novacomd
# Required-Start: $remote_fs dbus udev
# Required-Stop: $remote_fs dbus udev
# Should-Start: $syslog
# Should-Stop: $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: palm novacom daemon
# Description: Daemon for connecting to palm devices
### END INIT INFO

# Based on /etc/init.d/skeleton
# Edited by Members of the MTU LUG. lug.mtu.edu

# Do NOT "set -e"

# PATH should only include /usr/* if it runs after the mountnfs.sh script
PATH=/sbin:/usr/sbin:/bin:/usr/bin:/opt/Palm/novacom
DESC="Palm daemon to connect to webOS devices"
NAME=novacomd
DAEMON=/opt/Palm/novacom/$NAME
DAEMON_ARGS="--daemonize"
SCRIPTNAME=/etc/init.d/$NAME

# Exit if the package is not installed
[ -x "$DAEMON" ] || exit 0

# Read configuration variable file if it is present
[ -r /etc/default/$NAME ] && . /etc/default/$NAME

# Load the VERBOSE setting and other rcS variables
. /lib/init/vars.sh

# Define LSB log_* functions.
# Depend on lsb-base (>= 3.2-14) to ensure that this file is present
# and status_of_proc is working.
. /lib/lsb/init-functions

#
# Function that starts the daemon/service
#
do_start()
{
# Return
# 0 if daemon has been started
# 1 if daemon was already running
# 2 if daemon could not be started
start-stop-daemon --start --quiet --exec $DAEMON --test > /dev/null \
|| return 1
start-stop-daemon --start --quiet --exec $DAEMON -- \
$DAEMON_ARGS \
|| return 2
}

#
# Function that stops the daemon/service
#
do_stop()
{
# Return
# 0 if daemon has been stopped
# 1 if daemon was already stopped
# 2 if daemon could not be stopped
# other if a failure occurred
start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --name $NAME
RETVAL="$?"
[ "$RETVAL" = 2 ] && return 2
# Wait for children to finish too if this is a daemon that forks
# and if the daemon is only ever run from this initscript.
# If the above conditions are not satisfied then add some other code
# that waits for the process to drop all resources that could be
# needed by services started subsequently. A last resort is to
# sleep for some time.
start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
[ "$?" = 2 ] && return 2
# Many daemons don't delete their pidfiles when they exit.
rm -f $PIDFILE
return "$RETVAL"
}

#
# Function that sends a SIGHUP to the daemon/service
#
do_reload() {
#
# If the daemon can reload its configuration without
# restarting (for example, when it is sent a SIGHUP),
# then implement that here.
#
start-stop-daemon --stop --signal 1 --quiet --name $NAME
return 0
}

case "$1" in
start)
[ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
do_start
case "$?" in
0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
esac
;;
stop)
[ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME"
do_stop
case "$?" in
0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
esac
;;
status)
status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $?
;;
#reload|force-reload)
#
# If do_reload() is not implemented then leave this commented out
# and leave 'force-reload' as an alias for 'restart'.
#
#log_daemon_msg "Reloading $DESC" "$NAME"
#do_reload
#log_end_msg $?
#;;
restart|force-reload)
#
# If the "reload" option is implemented then remove the
# 'force-reload' alias
#
log_daemon_msg "Restarting $DESC" "$NAME"
do_stop
case "$?" in
0|1)
do_start
case "$?" in
0) log_end_msg 0 ;;
1) log_end_msg 1 ;; # Old process is still running
*) log_end_msg 1 ;; # Failed to start
esac
;;
*)
# Failed to stop
log_end_msg 1
;;
esac
;;
*)
#echo "Usage: $SCRIPTNAME {start|stop|restart|reload|force-reload}" >&2
echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2
exit 3
;;
esac

:
</pre>

4. Run:

<pre>
update-rc.d novacomd defaults
</pre>

Adding flash support

2011-03-29T20:50:44Z

Loudergood: /* Step 5. Wrap Up */

== Adobe Flash ==
Adobe Flash is not included in this webOS 2.1 doctor, but can be added with files from a VZW Pre 2 2.0.1 doctor.

=== Adding Flash Support ===
The easiest way to enable Adobe Flash on your webOS 2.1.0 legacy device is by creating a modular package and installing that, along with a patch to make the Adobe Flash preferences visible in the browser.

----

==== Step 1. Prerequisites ====
*Download the Verizon 2.0.1 Pre 2 Doctor ([http://palm.cdnetworks.net/rom/pre2/p201r0d02172011/ver1z0np201rod/webosdoctorp102verizonwireless.jar here])
*Download Jason Robitaille's IPK Packager ([http://code.google.com/p/ipk-packager/downloads/list here])
*Download webOS Quick Install ([http://forums.precentral.net/canuck-coding/274461-webos-quick-install-v4-04-a.html here])
*Download temporary directory ([http://forums.precentral.net/attachments/canuck-coding/56009d1298772359-how-get-flash-legacy-devices-2-1-0-flashplugincontainer.zip here]) and unzip the FlashPluginContainer folder to your desktop
*Download patch to enable Flash preferences in the browser ([http://forums.precentral.net/attachments/canuck-coding/55913d1298547118-how-get-flash-legacy-devices-2-1-0-show-flash-prefs-legacy-devices.patch here])

==== Step 2. Unpack ====
*Open the 2.0.1 doctor with an archive manager, like 7zip. Navigate to "<code>resources/webOS.tar/./nova-cust-image-roadrunner.rootfs.tar.gz/./</code>" This is where the Flash files are stored.
*Extract the following files from the webOS ROM:

<blockquote>/etc/adobe/mms.cfg
 /etc/adobe/oem.cfg
 /usr/lib/BrowserServerPlugins/libflashplayer.so
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play-down.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/resource/plugin-scrim.png
 /usr/lib/libFlashGraphics.so
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-scrim.png
 /usr/lib/BrowserServerPlugins/FlashMiniPlugin.so</blockquote>

==== Step 3. Drag 'N' Drop ====
*Simply place the files from the ROM into the FlashPluginContainer folder in their respective locations.
*Pay close attention to where each file/folder is stored inside the webOS ROM.

==== Step 4. Packaging ====
*Open Jason's IPK Packager and point the program to the '''files''' folder. Do NOT point to FlashPluginContainer, as the install will fail.
*The rest of the fields will populate on their own.
*Save the IPK file somewhere using "Create IPK Package." You may want to keep it handy.

==== Step 5. Wrap Up ====
*Use webOS Quick Install to install both IPK and patch.

Note: The patch to enable Flash preferences is also available in Preware.

Note: People are reporting problems with installing the IPK with WOSQI v4.04, installing it via Preware seems to work well.

==== Step 6. Edit system files ====
''Obsolete as of 21/03/2011.''

Open /usr/palm/applications/com.palm.app.browser/app/controllers/preferences-assistant.js (either in your MetaDoctor or on your live device -if on a live device, remember to make a backup!)
: Find the following two lines (should be lines 46 & 47) and comment them out by adding // to the beginning of each line:
<blockquote>this.controller.get("flashPref").hide();
 this.controller.get("autoLoadPref").hide(); </blockquote>

==== Step 7. Reboot ====
Reboot your devices for changes to take effect

Support thread: http://forums.precentral.net/canuck-coding/276703-how-get-flash-legacy-devices-2-1-0-a.html

----

=== Adding Flash Support Manually ===
# Extract WebOS.tar from the Resources folder in the VZW doctor to a location on your hard drive 
# Copy the following files from the extracted WebOS.tar to their equivalent locations in your MetaDoctor (alternatively, you can copy them manually to a live device using Novaterm)
<blockquote>/etc/adobe/mms.cfg
 /etc/adobe/oem.cfg
 /usr/lib/BrowserServerPlugins/libflashplayer.so
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play-down.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/resource/plugin-scrim.png
 /usr/lib/libFlashGraphics.so
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-scrim.png
 /usr/lib/BrowserServerPlugins/FlashMiniPlugin.so</blockquote>
:3. Open /usr/palm/applications/com.palm.app.browser/app/controllers/preferences-assistant.js (either in your MetaDoctor or on your live device -if on a live device, remember to make a backup!)
: Find the following two lines (should be lines 46 & 47) and comment them out by adding // to the beginning of each line:
<blockquote>this.controller.get("flashPref").hide();
 this.controller.get("autoLoadPref").hide(); </blockquote>
:4. Reboot your Pre if the editing was done on a live device

Flash preferences should now be visible under browser preferences.

----

=== Flash Troubleshooting ===
After adding Flash support, you may find that visiting any page with the browser will never completely load, and then automatically refresh in a loop. Disabling and the enabling Flash content in the browser preferences will fix this issue.

Adding flash support

2011-03-29T20:50:13Z

Loudergood: /* Step 5. Wrap Up */

== Adobe Flash ==
Adobe Flash is not included in this webOS 2.1 doctor, but can be added with files from a VZW Pre 2 2.0.1 doctor.

=== Adding Flash Support ===
The easiest way to enable Adobe Flash on your webOS 2.1.0 legacy device is by creating a modular package and installing that, along with a patch to make the Adobe Flash preferences visible in the browser.

----

==== Step 1. Prerequisites ====
*Download the Verizon 2.0.1 Pre 2 Doctor ([http://palm.cdnetworks.net/rom/pre2/p201r0d02172011/ver1z0np201rod/webosdoctorp102verizonwireless.jar here])
*Download Jason Robitaille's IPK Packager ([http://code.google.com/p/ipk-packager/downloads/list here])
*Download webOS Quick Install ([http://forums.precentral.net/canuck-coding/274461-webos-quick-install-v4-04-a.html here])
*Download temporary directory ([http://forums.precentral.net/attachments/canuck-coding/56009d1298772359-how-get-flash-legacy-devices-2-1-0-flashplugincontainer.zip here]) and unzip the FlashPluginContainer folder to your desktop
*Download patch to enable Flash preferences in the browser ([http://forums.precentral.net/attachments/canuck-coding/55913d1298547118-how-get-flash-legacy-devices-2-1-0-show-flash-prefs-legacy-devices.patch here])

==== Step 2. Unpack ====
*Open the 2.0.1 doctor with an archive manager, like 7zip. Navigate to "<code>resources/webOS.tar/./nova-cust-image-roadrunner.rootfs.tar.gz/./</code>" This is where the Flash files are stored.
*Extract the following files from the webOS ROM:

<blockquote>/etc/adobe/mms.cfg
 /etc/adobe/oem.cfg
 /usr/lib/BrowserServerPlugins/libflashplayer.so
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play-down.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/resource/plugin-scrim.png
 /usr/lib/libFlashGraphics.so
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-scrim.png
 /usr/lib/BrowserServerPlugins/FlashMiniPlugin.so</blockquote>

==== Step 3. Drag 'N' Drop ====
*Simply place the files from the ROM into the FlashPluginContainer folder in their respective locations.
*Pay close attention to where each file/folder is stored inside the webOS ROM.

==== Step 4. Packaging ====
*Open Jason's IPK Packager and point the program to the '''files''' folder. Do NOT point to FlashPluginContainer, as the install will fail.
*The rest of the fields will populate on their own.
*Save the IPK file somewhere using "Create IPK Package." You may want to keep it handy.

==== Step 5. Wrap Up ====
*Use webOS Quick Install to install both IPK and patch.

Note: The patch to enable Flash preferences is also available in Preware.
Note: People are reporting problems with installing the IPK with WOSQI v4.04, installing it via Preware seems to work well.

==== Step 6. Edit system files ====
''Obsolete as of 21/03/2011.''

Open /usr/palm/applications/com.palm.app.browser/app/controllers/preferences-assistant.js (either in your MetaDoctor or on your live device -if on a live device, remember to make a backup!)
: Find the following two lines (should be lines 46 & 47) and comment them out by adding // to the beginning of each line:
<blockquote>this.controller.get("flashPref").hide();
 this.controller.get("autoLoadPref").hide(); </blockquote>

==== Step 7. Reboot ====
Reboot your devices for changes to take effect

Support thread: http://forums.precentral.net/canuck-coding/276703-how-get-flash-legacy-devices-2-1-0-a.html

----

=== Adding Flash Support Manually ===
# Extract WebOS.tar from the Resources folder in the VZW doctor to a location on your hard drive 
# Copy the following files from the extracted WebOS.tar to their equivalent locations in your MetaDoctor (alternatively, you can copy them manually to a live device using Novaterm)
<blockquote>/etc/adobe/mms.cfg
 /etc/adobe/oem.cfg
 /usr/lib/BrowserServerPlugins/libflashplayer.so
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play-down.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/resource/plugin-scrim.png
 /usr/lib/libFlashGraphics.so
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-scrim.png
 /usr/lib/BrowserServerPlugins/FlashMiniPlugin.so</blockquote>
:3. Open /usr/palm/applications/com.palm.app.browser/app/controllers/preferences-assistant.js (either in your MetaDoctor or on your live device -if on a live device, remember to make a backup!)
: Find the following two lines (should be lines 46 & 47) and comment them out by adding // to the beginning of each line:
<blockquote>this.controller.get("flashPref").hide();
 this.controller.get("autoLoadPref").hide(); </blockquote>
:4. Reboot your Pre if the editing was done on a live device

Flash preferences should now be visible under browser preferences.

----

=== Flash Troubleshooting ===
After adding Flash support, you may find that visiting any page with the browser will never completely load, and then automatically refresh in a loop. Disabling and the enabling Flash content in the browser preferences will fix this issue.

Novacomd Init Script

2011-03-01T22:56:57Z

Loudergood: Replaced content with 'See http://www.webos-internals.org/wiki/Accessing_Linux_Debian'

See http://www.webos-internals.org/wiki/Accessing_Linux_Debian

WebOS Internals PDK

2011-02-23T01:37:30Z

Loudergood: /* Setup Scratchbox */

[[Category: SDL]]
Palm's binary sdk the "Plugin Developer Kit" became available to all developers in March 2010.

When the widk was developed, the Palm PDK didn't exist, and until Dec 2010, it was not possible to run the PDK in Linux. If you would like to run the official Palm PDK, see [[PDK on Linux]] for directions.

In addition to the PDK, webOS Internals has released a full "WIDK" (webOS Internals Development Kit) for you using Scratchbox2.

Less than 10% of developers in the webOS developer community use Linux variants. Among those 10% there are dozens of different linux distributions that people use. Palm, therefore has chosen to support only Mac and Windows platforms for their PDK. Palm reccomends that Linux based developers use the webOS-internals WIDK instead.

We ''strongly'' urge the open-source homebrew community to standardize on this WIDK. It uses the same underlying technologies, and is entirely open.

Scratchbox 2 is a cross-compilation engine, it can be used to create a highly flexible SDK.

As installed below, the install process uses a script which extracts the required Palm provided files from a copy of webOS doctor, and downloads from other sources, and builds a complete compilation environment automatically which can compile SDL and openGLES apps for webOS.

SB2 ''itself'' is totally distribution neutral but the webOS cross-compile environment is designed and tested on Ubuntu 9.10 32 bit. (At least one user in #webos-internals reports complete success running the cross compile environment in Ubuntu 9.10 64 bit after installing curl via apt-get.) See [[WebOS_Internals_PDK_on_Mandriva]] if you want to run it on Mandriva. If you want to run the WIDK on other distributions and are willing to support that yourself and not ask webOS Internals any questions about it then please enjoy and if you succeed come back here and make a new article on how you did it. Otherwise, use the recommended OS.

The webOS Internals team ''strongly suggest'' apt-get install into the Ubuntu environment only for this purpose. The same installation of Sun Virtualbox which hosts the Palm SDK emulator can host an Ubuntu 9.10 server with very little effort on any operating system.

Developers wanting to work in an open environment 'without' SB2 can consider using the [[PuffTheMagic NDK]].

==SB2 Homepage==
[http://www.freedesktop.org/wiki/Software/sbox2 http://www.freedesktop.org/wiki/Software/sbox2]pdk

==License==
Scratchbox 2 is distributed under LGPL version 2.1, portions are under GPL version 2. Some minor stuff is under MIT style license.

== Installation on Ubuntu for webOS PDK cross compiling ==

If setting up in a Virtual Box instance, it is recommended that you first complete the openSSH config as described in the VirtualBox tips for Windows users to the right. This is helpful even with a Linux host, as SSH into the PDK Virtual Machine will allow copy and paste of the commands listed below and reduce errors.

== Update ==
There is an automated installer avaliable [http://forums.precentral.net/webos-internals/266139-webos-internals-automated-installers.html#post2718551 here]

<div style="float:right; clear:right; width:30%">{{Ubuntu_VM_notes_for_Windows_users}}</div>
===Toolchain===

===Prerequisites===
Your Ubuntu installation will need the following installed. If you do not have them, run the command after the package name. You can test if they are found by just typing the command name. If it says command not found, you need to install it.

{| border="1"
|+
|'''git''' || sudo apt-get install git-core
|-
|'''gcc''' || sudo apt-get install build-essential
|-
|'''curl''' || sudo apt-get install curl
|-
|'''unzip'''|| sudo apt-get install unzip
|-
|'''autoconf'''|| sudo apt-get install autoconf
|-
|'''subversion'''|| sudo apt-get install subversion
|-
|'''libtool'''|| sudo apt-get install libtool
|-
|'''wget'''|| sudo apt-get install wget
|-
|'''pkg-config'''|| sudo apt-get install pkg-config
|-
|'''gettext'''|| sudo apt-get install gettext
|-
|'''fakeroot'''|| sudo apt-get install fakeroot
|-
|'''javac'''|| sudo apt-get install sun-java6-jdk
|-
|'''ant'''|| sudo apt-get install ant
|-
|'''xsltproc'''|| sudo apt-get install xsltproc
|-
|'''intltool'''|| sudo apt-get install intltool
|-
|'''mkimage'''|| sudo apt-get install uboot-mkimage
|-
|'''lsdiff'''|| sudo apt-get install patchutils
|-
|'''flex'''|| sudo apt-get install flex
|-
|'''bison'''|| sudo apt-get install bison
|-
|'''libssl-dev'''|| sudo apt-get install libssl-dev
|-
|'''libz-dev'''|| sudo apt-get install libz-dev
|-
|'''libbz2-dev'''|| sudo apt-get install libbz2-dev
|-
|'''xar'''|| sudo apt-get install xar
|-
|'''help2man'''|| sudo apt-get install help2man
|-
|'''texinfo'''|| sudo apt-get install texinfo
|-
|'''automake 1.10'''|| sudo apt-get install automake1.10
|-
|'''autopoint'''|| sudo apt-get install autopoint
|}

* it has been reported that sun-java6-jdk isn't necessary

If you're uncertain at all, just cut and paste the following. If they are already installed, they'll be skipped.

sudo apt-get install git-core build-essential curl unzip autoconf subversion libtool wget pkg-config gettext fakeroot ant xsltproc intltool uboot-mkimage patchutils flex bison libssl-dev libz-dev libbz2-dev xar help2man texinfo automake1.10 autopoint

'''Note:''' If you are a beginner with Ubuntu Linux Distribution, you should update all the packages on your system to avoid problems when you will compile.

'''Note 2:''' If you're using Ubuntu and <code>xar</code> cannot be installed with <code>sudo apt-get install xar</code>, then you have to download two <code>.deb</code>-files manually and install them (in the order they are listed):
# [http://packages.ubuntu.com/hardy/libxar1 libxar1]
# [http://packages.ubuntu.com/hardy/xar xar]
After that execute the above command again.

Use these 2 command line : 
Update repositories :
sudo aptitude update
And next, update the packages :
sudo aptitude safe-upgrade

If you're on a 64-bit system, you will also need to install the ia32-libs package.

'''Note:''' The ''make toolchain'' command and later steps will download approximately a half-gig of tools and sources from various locations. Do not start this if you do not have time for a large download. Additionally, if you already have downloaded a copy of the correct version of the WebOS doctor, you can reduce the download time by copying the doctor file into cross-compile/doctors/ with the correct name. This will cause the appropriate command to skip that download. Note that codesourcery rate limts downloads and at a minimum this process will take 10 to 15 minutes irrespective of your connection speed.

====Start setup====
Create a preware folder, copy the cross-compile tools into it (if you have not installed git, apt-get install git-core), and use a make script to begin the set up of the compilation toolchain.

sudo mkdir -p /srv/preware
cd /srv/preware
sudo chmod 777 .
git clone git://git.webos-internals.org/preware/cross-compile.git
cd cross-compile
make toolchain

If errors occur, browse the [http://git.webos-internals.org/?p=preware/cross-compile.git;a=shortlog repository online] and checkout earlier commits until you get something that gets through "make toolchain" and the later "make stage" commands like so:

git checkout <commit-ish>

====Fix mmap errors====
The following commands appear redundant. They are not. The install this fixes your mmap config to fix an mmap: permission denied error, but we don't need the package itself. (Do each command separately with cut and paste).

sudo apt-get install qemu-arm-static
sudo apt-get remove qemu-arm-static

: OR As a workaround, if this package is not available,
::: the following commands can be executed in a root shell (sudo -s) to fix the mmap configuration to enable qemu-arm to work.

echo "vm.mmap_min_addr = 4096" > /etc/sysctl.d/mmap_min_addr.conf
/etc/init.d/procps restart

(note that the value should not be "0". 4096 is chosen to avoid null pointer attacks.)

====Verify sh shell====
On Ubuntu /bin/sh is a symbolic link to dash. This will cause errors with the make stage command below, as some of the scripts assume bash. Run the following command to see what shell sh is linked to.

ls -l /bin/sh

If the result is a link to dash:

lrwxrwxrwx 1 root root 4 2010-07-06 23:55 /bin/sh -> dash

You will want to correct it with the following:

sudo dpkg-reconfigure dash

You will be asked if you want to "Install dash as /bin/sh?". Select "<No>" and bash will be used. Rerun the command to verify:

ls -l /bin/sh

You should now see:

lrwxrwxrwx 1 root root 4 2010-07-09 21:12 /bin/sh -> bash

====Setup Scratchbox====
Now, use apt-get to setup scratchbox...

sudo apt-get install scratchbox2 qemu-kvm-extras (in Debian install qemu-user and qemu-system instead of qemu-kvm-extras)

...and set it up for compiling for webOS.

cd /srv/preware/cross-compile/toolchain/arm-2007q3/arm-none-linux-gnueabi/libc
PATH=/srv/preware/cross-compile/toolchain/arm-2007q3/bin:${PATH} sb2-init -c /usr/bin/qemu-arm armv7 arm-none-linux-gnueabi-gcc
cd /srv/preware/cross-compile

Then:

make stage

Once this setup is complete, compiling sdl apps for webOS is very simple.

==Verified installed clean list==

If you have successfully built the WIDK from scratch, with NO problems, feel free to add your information to this list. This will help us assess what distributions and versions it is fully compatible with.

{| border="1" class="wikitable"
|-
|'''IRC name'''
|'''Linux Distribution'''
|'''Version'''
|'''Date'''
|'''Comments'''
|-
|Scoutcamper
|Ubuntu
|9.04,9.10,10.04,10.10
|10-18-10
|Works Great!
|}

It just doesn't work tried for over a week, with fresh Ubuntu 10.4 inside and outside of virtual box, fails on libtool for common/fuse/. Tried -j4 option with make stage, tried make staging-armv7. Also installed automake-1.9 after seeing complaints about that. -- please sign your comments

==Errors during make stage ==

===automake1.10===

If you see the error below, you need the latest automake (1.10)

/usr/share/automake-1.9/am/depend2.am: am__fastdepOBJC does not appear in AM_CONDITIONAL
configure.in:88: installing `./config.guess'
configure.in:88: installing `./config.sub'
Makefile.am: installing `./INSTALL'
autoreconf2.50: automake failed with exit status: 1

Install automake1.10 and it should work (according to [http://old.nabble.com/AC_PROG_OBJC-and-automake-1.9-td22434760.html this page])

===Libtool===

make[5]: Entering directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6/src'
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Wall -g -O2 -MT libdotconf_la-dotconf.lo -MD -MP -MF .deps/libdotconf_la-dotconf.Tpo -c -o libdotconf_la-dotconf.lo `test -f 'dotconf.c' || echo './'`dotconf.c
libtool: Version mismatch error. This is libtool 2.2.6b, but the
libtool: definition of this LT_INIT comes from libtool 2.2.6.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6b
libtool: and run autoconf again.
make[5]: *** [libdotconf_la-dotconf.lo] Error 63
make[5]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6/src'
make[4]: *** [install-recursive] Error 1
make[4]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6'
make[3]: *** [build/armv6.built] Error 2
make[3]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf'
make[2]: *** [build_common/libdotconf] Error 2
make[2]: Leaving directory `/srv/preware/cross-compile'
make[1]: *** [staging-armv6] Error 2
make[1]: Leaving directory `/srv/preware/cross-compile'
make: *** [stage] Error 2

Confirmed by 3 people. Fix this by either (your choice)
*upgrading to Ubuntu 10.04 or newer (the WIDK now relies on a slightly newer version of libtool that's not in 9.10 or earlier)
*updating libtool to 2.2.6b-2 (backported to 9.10, see available downloads on http://linuxappfinder.com/package/libtool#ubuntu_karmicpartner)

If you're getting an error where sb2-init gives you the following output:

checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

Running /usr/bin/sb2-build-libtool failed
You can run this manually later, otherwise your
sb2 environment is correctly setup and ready to use

You need to upgrade qemu. Alternatively, if your sb2-init output fails with a different output, like this:

checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

sb2-init completed successfully, have fun!

Then you need to upgrade scratchbox, too (install 2.0 instead of 1.99).

=== ecore ===
*TRUE and FALSE are not defined:
Manually add the definition:

#ifndef TRUE
# define TRUE 1
#endif

#ifndef FALSE
# define FALSE 0
#endif

*<code>$po_makefile_in</code> could not be found:
**Open the file <code>/srv/preware/cross-compile/packages/dev-e/ecore/build/src/configure.ac</code> and search for the line with: <code>$po_makefile_in</code> (in my case line 1437) and replace it with <code>po/Makefile.in</code>

=== /bin/sh errors ===
If you are getting a "bad fd number" or other /bin/sh error, make sure your /bin/sh points to bash, not another shell (such as dash.)

Go back through the Verify sh shell section above to correct.

=== fuse ===
If you get an error like this (happened to me on Ubuntu 10.10):

make[5]: Entering directory '/srv/preware/cross-compile/packages/common/fuse/build/armv7/lib'
if /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DFUSERMOUNT_DIR=\"/usr/local/bin\" -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DFUSE_USE_VERSION=26 -Wall -W -Wno-sign-compare -Wstrict-prototypes -Wmissing-declarations -Wwrite-strings -g -O2 -fno-strict-aliasing -MT fuse.lo -MD -MP -MF ".deps/fuse.Tpo" -c -o fuse.lo fuse.c; \
then mv -f ".deps/fuse.Tpo" ".deps/fuse.Plo"; else rm -f ".deps/fuse.Tpo"; exit 1; fi
libtool: Version mismatch error. This is libtool 2.1a Debian 1.9+20051221-1, but the
libtool: definition of this LT_INIT comes from libtool 2.2.6b.
libtool: You should recreate aclocal.m4 with macros from libtool 2.1a Debian 1.9+20051221-1
libtool: and run autoconf again.
make[5]: *** [fuse.lo] Error 1
make[5]: Leaving direcotry '/srv/preware/cross-compile/packages/common/fuse/build/armv7/lib'

Then open the file <code>/srv/preware/cross-compile/packages/common/fuse/build/src/ltmain.sh</code> and search for <code>exit $EXIT_MISMATCH</code> (in my case line 1028) and comment it out by placing a <code>#</code> before this line. I know that's a dirty fix, but it worked for me. Note that you will see the same error messages as before, but it won't stop there.

==Sample build of [[Application:Doom]]==

Now, go to [[Building DOOM with scratchbox2]] and follow the simple directions.

==In Process Enhancements==
[[Extracting the PDK on Linux]]

Novacomd Init Script

2011-02-21T18:41:42Z

Loudergood:

<source lang="bash">
#!/sbin/runscript

start() {
ebegin "Starting novacomd"
start-stop-daemon --start --background --exec /opt/Palm/novacom/novacomd
result=$?
eend $result
}

stop() {
ebegin "Stopping novacomd"
start-stop-daemon --stop --quiet --exec /opt/Palm/novacom/novacomd
result=$?
eend $result
}
</source>

== For Debian(tested on Sid 2/21/2011) ==

1. Save this at /etc/init.d/novacomd
2. Make sure you make it executable. Use "chmod +x /etc/init.d/novacomd"
3. Run "update-rc.d novacomd defaults"

<source lang="bash">
#! /bin/sh
### BEGIN INIT INFO
# Provides: novacomd
# Required-Start: $remote_fs dbus udev
# Required-Stop: $remote_fs dbus udev
# Should-Start: $syslog
# Should-Stop: $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: palm novacom daemon
# Description: Daemon for connecting to palm devices
#
### END INIT INFO

PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/opt/Palm/novacom
DESC="Palm Novacom daemon"
NAME="novacomd"

DAEMON=/opt/Palm/novacom/$NAME

PIDFILE=/var/run/$NAME.pid

SCRIPTNAME=/etc/init.d/novacomd

# Gracefully exit if the package has been removed.
test -x $DAEMON || exit 0

. /lib/lsb/init-functions

#
# Function that starts the daemon/service.
#
d_start() {
start-stop-daemon --start --quiet --pidfile $PIDFILE \
--exec $DAEMON -- $DAEMON_OPTS
}

#
# Function that stops the daemon/service.
#
d_stop() {
start-stop-daemon --stop --retry 5 --quiet --pidfile $PIDFILE \
--exec $DAEMON
}

case "$1" in
start)
log_daemon_msg "Starting $DESC" "$NAME"
d_start
case "$?" in
0) log_end_msg 0 ;;
1) log_progress_msg "already started"
log_end_msg 0 ;;
*) log_end_msg 1 ;;
esac
;;
stop)
log_daemon_msg "Stopping $DESC" "$NAME"
d_stop
case "$?" in
0) log_end_msg 0 ;;
1) log_progress_msg "already stopped"
log_end_msg 0 ;;
*) log_end_msg 1 ;;
esac
;;
restart|force-reload)
$0 stop
$0 start
;;
status)
status_of_proc -p $PIDFILE $DAEMON $NAME && exit 0 || exit $?
;;
*)
echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload|status}" >&2
exit 1
;;
esac

exit 0
</source>

Novacomd Init Script

2011-02-21T18:40:21Z

Loudergood: adding debian init instructions.

<source lang="bash">
#!/sbin/runscript

start() {
ebegin "Starting novacomd"
start-stop-daemon --start --background --exec /opt/Palm/novacom/novacomd
result=$?
eend $result
}

stop() {
ebegin "Stopping novacomd"
start-stop-daemon --stop --quiet --exec /opt/Palm/novacom/novacomd
result=$?
eend $result
}
</source>

For Debian(tested on Sid 2/21/2011)
1. Save this at /etc/init.d/novacomd
2. Make sure you make it executable. Use "chmod +x /etc/init.d/novacomd"
3. Run "update-rc.d novacomd defaults"

<source lang="bash">
#! /bin/sh
### BEGIN INIT INFO
# Provides: novacomd
# Required-Start: $remote_fs dbus udev
# Required-Stop: $remote_fs dbus udev
# Should-Start: $syslog
# Should-Stop: $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: palm novacom daemon
# Description: Daemon for connecting to palm devices
#
### END INIT INFO

PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/opt/Palm/novacom
DESC="Palm Novacom daemon"
NAME="novacomd"

DAEMON=/opt/Palm/novacom/$NAME

PIDFILE=/var/run/$NAME.pid

SCRIPTNAME=/etc/init.d/novacomd

# Gracefully exit if the package has been removed.
test -x $DAEMON || exit 0

. /lib/lsb/init-functions

#
# Function that starts the daemon/service.
#
d_start() {
start-stop-daemon --start --quiet --pidfile $PIDFILE \
--exec $DAEMON -- $DAEMON_OPTS
}

#
# Function that stops the daemon/service.
#
d_stop() {
start-stop-daemon --stop --retry 5 --quiet --pidfile $PIDFILE \
--exec $DAEMON
}

case "$1" in
start)
log_daemon_msg "Starting $DESC" "$NAME"
d_start
case "$?" in
0) log_end_msg 0 ;;
1) log_progress_msg "already started"
log_end_msg 0 ;;
*) log_end_msg 1 ;;
esac
;;
stop)
log_daemon_msg "Stopping $DESC" "$NAME"
d_stop
case "$?" in
0) log_end_msg 0 ;;
1) log_progress_msg "already stopped"
log_end_msg 0 ;;
*) log_end_msg 1 ;;
esac
;;
restart|force-reload)
$0 stop
$0 start
;;
status)
status_of_proc -p $PIDFILE $DAEMON $NAME && exit 0 || exit $?
;;
*)
echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload|status}" >&2
exit 1
;;
esac

exit 0
</source>

PDK on Linux

2010-12-28T20:08:03Z

Loudergood: /* Prerequisites */

The official Palm PDK development kit for writing native programs is not supported on Linux.

The instructions on this page should allow you to get the official Palm webOS PDK for OSX working on Linux.

It's totally untested other than running a few scripts and confirming that things seem to be where they should be, so please confirm if it works for you.

==Prerequisites==
* Get the command line tool "xar". Some debian based systems have it, try apt-get install xar. If not found, get it from http://code.google.com/p/xar/ (I needed package libxml2-dev to compile it) (I also needed openssl-dev to compile it on Ubuntu 10.10)
* You will need to have git installed to retrieve files from the WIDK repository.
* Building the pkg file requires Curl and libbz2-dev
* Since you're planning to write native software for webOS, this assumes you have things like gcc and make and normal developer stuff like that.

We will be using tools found in the WIDK cross-compile repository is really helpful as it already has functionality to download and extract the OSX PDK, most of which will "just work" on Linux. Tools found in the WIDK repository can also download the CodeSourcery toolchain for Linux to replace the one included in the PDK, built for Darwin.

==Setup==
===Get the Palm PDK using the Webos-Internals makefile===

This downloads Palm's DMG file, downloads and patches a tool for converting DMG's, and runs it against the Palm DMG, ending up with a Xar format package file. (filename ends in .pkg)

<pre style="margin-left:50px;">
git clone git://git.webos-internals.org/preware/cross-compile.git
cd cross-compile
make doctors/Palm_webOS_SDK-Mac-1.4.5.465.pkg
</pre>

You now have a Palm_webOS_SDK-Mac-1.4.5.465.pkg in doctors/ .

===Extract that .pkg file===

Now let's extract it into / (this will create /opt/PalmPDK)

<pre style="margin-left:50px;">
xar -xf doctors/Palm_webOS_SDK-Mac-1.4.5.465.pkg palmpdk.pkg
sudo sh -c 'gzip -cd palmpdk.pkg/Payload | (cd /; cpio -i)'
</pre>

You now have a Palm PDK in /opt/PalmPDK, but you don't have a working cross-compile toolchain, because the one Palm supplied was for osX / Darwin not Linux. We need to fix that.

===Get CodeSourcery Linux cross-compiler===
Install the CodeSourcery Linux cross-compiler toolchain where Palm's toolchain built for OSX was.

<pre style="margin-left:50px">
make toolchain
sudo cp -r toolchain/arm-2007q3 /opt/PalmPDK
cd /opt/PalmPDK
sudo mv arm-gcc arm-gcc-darwin
sudo ln -s arm-2007q3 arm-gcc
</pre>

Someone who is familiar with the PDK should test this at this point to see if you can actually use it in the proper ways.

PDK on Linux

2010-12-28T20:05:44Z

Loudergood: /* Prerequisites */

The official Palm PDK development kit for writing native programs is not supported on Linux.

The instructions on this page should allow you to get the official Palm webOS PDK for OSX working on Linux.

It's totally untested other than running a few scripts and confirming that things seem to be where they should be, so please confirm if it works for you.

==Prerequisites==
* Get the command line tool "xar". Some debian based systems have it, try apt-get install xar. If not found, get it from http://code.google.com/p/xar/ (I needed package libxml2-dev to compile it) (I also needed openssl-dev to compile it on Ubuntu 10.10)
* You will need to have git installed to retrieve files from the WIDK repository.
* Since you're planning to write native software for webOS, this assumes you have things like gcc and make and normal developer stuff like that.

We will be using tools found in the WIDK cross-compile repository is really helpful as it already has functionality to download and extract the OSX PDK, most of which will "just work" on Linux. Tools found in the WIDK repository can also download the CodeSourcery toolchain for Linux to replace the one included in the PDK, built for Darwin.

==Setup==
===Get the Palm PDK using the Webos-Internals makefile===

This downloads Palm's DMG file, downloads and patches a tool for converting DMG's, and runs it against the Palm DMG, ending up with a Xar format package file. (filename ends in .pkg)

<pre style="margin-left:50px;">
git clone git://git.webos-internals.org/preware/cross-compile.git
cd cross-compile
make doctors/Palm_webOS_SDK-Mac-1.4.5.465.pkg
</pre>

You now have a Palm_webOS_SDK-Mac-1.4.5.465.pkg in doctors/ .

===Extract that .pkg file===

Now let's extract it into / (this will create /opt/PalmPDK)

<pre style="margin-left:50px;">
xar -xf doctors/Palm_webOS_SDK-Mac-1.4.5.465.pkg palmpdk.pkg
sudo sh -c 'gzip -cd palmpdk.pkg/Payload | (cd /; cpio -i)'
</pre>

You now have a Palm PDK in /opt/PalmPDK, but you don't have a working cross-compile toolchain, because the one Palm supplied was for osX / Darwin not Linux. We need to fix that.

===Get CodeSourcery Linux cross-compiler===
Install the CodeSourcery Linux cross-compiler toolchain where Palm's toolchain built for OSX was.

<pre style="margin-left:50px">
make toolchain
sudo cp -r toolchain/arm-2007q3 /opt/PalmPDK
cd /opt/PalmPDK
sudo mv arm-gcc arm-gcc-darwin
sudo ln -s arm-2007q3 arm-gcc
</pre>

Someone who is familiar with the PDK should test this at this point to see if you can actually use it in the proper ways.

PDK on Linux

2010-12-28T19:49:58Z

Loudergood: /* Prerequisites */

The official Palm PDK development kit for writing native programs is not supported on Linux.

The instructions on this page should allow you to get the official Palm webOS PDK for OSX working on Linux.

It's totally untested other than running a few scripts and confirming that things seem to be where they should be, so please confirm if it works for you.

==Prerequisites==
* Get the command line tool "xar". Some debian based systems have it, try apt-get install xar. If not found, get it from http://code.google.com/p/xar/ (I needed package libxml2-dev to compile it) (I needed openssl-dev to compile it)
* You will need to have git installed to retrieve files from the WIDK repository.
* Since you're planning to write native software for webOS, this assumes you have things like gcc and make and normal developer stuff like that.

We will be using tools found in theWIDK cross-compile repository is really helpful as it already has functionality to download and extract the OSX PDK, most of which will "just work" on Linux. Tools found in the WIDK repository can also download the CodeSourcery toolchain for Linux to replace the one included in the PDK, built for Darwin.

==Setup==
===Get the Palm PDK using the Webos-Internals makefile===

This downloads Palm's DMG file, downloads and patches a tool for converting DMG's, and runs it against the Palm DMG, ending up with a Xar format package file. (filename ends in .pkg)

<pre style="margin-left:50px;">
git clone git://git.webos-internals.org/preware/cross-compile.git
cd cross-compile
make doctors/Palm_webOS_SDK-Mac-1.4.5.465.pkg
</pre>

You now have a Palm_webOS_SDK-Mac-1.4.5.465.pkg in doctors/ .

===Extract that .pkg file===

Now let's extract it into / (this will create /opt/PalmPDK)

<pre style="margin-left:50px;">
xar -xf doctors/Palm_webOS_SDK-Mac-1.4.5.465.pkg palmpdk.pkg
sudo sh -c 'gzip -cd palmpdk.pkg/Payload | (cd /; cpio -i)'
</pre>

You now have a Palm PDK in /opt/PalmPDK, but you don't have a working cross-compile toolchain, because the one Palm supplied was for osX / Darwin not Linux. We need to fix that.

===Get CodeSourcery Linux cross-compiler===
Install the CodeSourcery Linux cross-compiler toolchain where Palm's toolchain built for OSX was.

<pre style="margin-left:50px">
make toolchain
sudo cp -r toolchain/arm-2007q3 /opt/PalmPDK
cd /opt/PalmPDK
sudo mv arm-gcc arm-gcc-darwin
sudo ln -s arm-2007q3 arm-gcc
</pre>

Someone who is familiar with the PDK should test this at this point to see if you can actually use it in the proper ways.