[maemo-developers] [maemo-developers] Documentation

[From: Kai Schindelka]

Pardon me for breaking the threading; I've subscribed only now, but
would like to jump in on this:

Philip Van Hoof spam at pvanhoof.be wrote:
> Also note that the scratchbox related documentation (on Maemo.org) is
> a bit outdated. And there's also a tiny issue with the d-bus package
> on the latest stable scratchbox release.

I wanted to play safe for the first try, went to [1] and downloaded the
installer script from [2].

Problem was, I'm deliberately using a small root partition. Running the
installer would fill it very quickly. Therefore I patched the script to
allow for an arbitrary destination directory. This seems to work, at
least as far as I can tell.
Question: Which address should I send the installer patch to?

Next I logged into Scratchbox and jumped to [3] -> Installation ->
Installing Xephyr:

[sbox-x86: ~] > fakeroot
sh-2.05b# apt-get update
sh-2.05b# apt-get install xserver-xephyr

Then I created the "start-xephyr.sh" script:

#!/bin/sh -e
prefix=/scratchbox/users/${LOGNAME}/targets/x86/usr
export LD_LIBRARY_PATH=${prefix}/lib; export LD_LIBRARY_PATH
exec ${prefix}/bin/Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac

Running the script from outside the Scratchbox I got the empty Xephyr
window. Then I continued with [4] and got a core dump after a bunch of
messages about non-existant directories below /home/${LOGNAME},
hildon-input-method and hildon-navigator. Restarting the script the User
interface then showed up as expected, although the directory and hildon
errors repeated.

After rebooting the machine (for testing) I was able to login and start
the User interface again. Note that I previously had configured sudo to
allow the user to mount the devices. - SB_DIR be the Scratchbox install
directory, LOGNAME the user configured to use the Scratchbox:

$ cd ${SB_DIR}
$ users/${LOGNAME}/home/${LOGNAME}/start-xephyr.sh &
$ sudo sbin/sbox_mount_all
$ ./login
[sbox-x86: ~] > export DISPLAY=127.0.0.1:2
[sbox-x86: ~] > af-sb-init.sh start

After that I successfully compiled and ran maemopad from [5].

Questions:
- Is this a resonable way to get started or is there a better way to do
  it?
- What about the errors on the first start, are they known or are they
  possibly my fault? Host is an i686 running Debian Etch.

> I'd be nice to update this documentation (and fix the d-bus package).
> I think many newcomers will have troubles trying to get the scratchbox
> environment working cause of this outdated info.

True, it is rather confusing having [2] and [3] differ. What do you
think about migrating [3] to the Wiki, so that this chapter can be
updated more easily? The Tutorial should have a link to a Wiki page
with updates and corrections at least, I'd suggest.

URLs:

[1] http://www.maemo.org/downloads/download-sdk.html
[2] http://repository.maemo.org/stable/1.0/installer/
[3]
http://www.maemo.org/platform/docs/tutorials/Maemo_tutorial.html#settingup
[4]
http://www.maemo.org/platform/docs/tutorials/Maemo_tutorial.html#Application-Framework-environment
[5]
http://repository.maemo.org/stable/1.0/applications/maemopad/maemopad_1.1.tar.gz

-- 
Bye; Kai