Customizing the Openmoko Distribution/de - Revision history

Kempelen: -Guides, -Applications, +Application Developers, +System Developers

2008-09-12T21:52:23Z

-Guides, -Applications, +Application Developers, +System Developers

Kempelen: Cateogry changes: -Openmoko/de

2008-09-07T11:42:53Z

Cateogry changes: -Openmoko/de

Dolfje at 07:57, 27 August 2008

2008-08-27T07:57:22Z

DolfjeBot1: Replacing 'OpenMoko' with 'Openmoko'

2008-08-22T22:47:17Z

Replacing 'OpenMoko' with 'Openmoko'

Proton: /* Setting Up the Openmoko Environment */

2008-07-31T12:14:12Z

‎Setting Up the Openmoko Environment

Proton: /* Was ist das Ziel? */

2008-07-31T12:13:06Z

‎Was ist das Ziel?

Proton: /* Was ist das Ziel? */

2008-07-31T12:03:49Z

‎Was ist das Ziel?

Proton: /* Was ist das Ziel? */

2008-07-31T12:02:22Z

‎Was ist das Ziel?

Proton: /* What's the goal? */

2008-07-31T11:56:46Z

‎What's the goal?

Proton: New page: == What's the goal? == The goal of this page is to teach you how to take an application that you've coded (or the sample app) and properly get it included in your rootfs. This article is ...

2008-07-31T11:51:34Z

New page: == What's the goal? == The goal of this page is to teach you how to take an application that you've coded (or the sample app) and properly get it included in your rootfs. This article is ...

New page

== What's the goal? ==

The goal of this page is to teach you how to take an application that you've coded (or the sample app) and properly get it included in your rootfs. This article is a bit of an aggregate page, it's going to take information from [[MokoMakefile]], [[User:CesarB/Using a local overlay|Using a local overlay]], [[Building a hello world application]], and [[Create a package from existing sources]]. So as you can see the goal is for it to be a very thorough introduction, and will take you from "Idea to Inclusion" of your application.

== Setting Up the Openmoko Environment ==

{| border="1" cellspacing="0" cellpadding="5"
|*If you already have the environment set up then it is imperative that you update your Makefile.
Do this by running:
<pre>make update-makefile</pre>
|}

This part of the tutorial is going to be pretty basic. I absolutely love [[MokoMakefile]] -- it's fantastic. The creator has done and continues to do a fantastic job with this. I see absolutely no reason not to use it. I put my OpenMoko development directory in /home/bryce/mokodev/ and it works great for me. You can feel free to do the same or put it anywhere else in your user directory (or anywhere on your system if you're feeling daring and a little nutty).

To get your environment set up, please get it set up according to [[MokoMakefile]]. However, if you do have the build environment set up manually and you're sure you know what you're doing, then feel free to go forward with this.

== Setting Up a Local Overlay ==
If you're at the point of setting up a local overlay, this means a couple things. First: you've had a brilliant idea for an application that you just need to have on the OpenMoko platform. Second: you realize that this killer app of yours needs to be done properly and you're not going to do anything silly like include it in the actual tree for the OpenMoko distro because it would probably end up just getting overwritten eventually, or you just realize that it's bad practice!

If you're wondering why and what a local overlay is then let me take this time to explain it to you. A local overlay is where you, as a developer, keep your local files in an OE style setup so that you can simply pull your updated code into the tree. You add your overlay tree into the bitbake setup so that when you call bitbake it will pull your own or your customized packages before going to the OE or OpenMoko trees. This keeps everything nice and organized for you and also allows you to build/rebuild/include your apps by using the [[MokoMakefile]]

Thank you to [[User:CesarB]] for this part of the wiki.

To create a local overlay:

* Create a "local" directory and its subdirectories (in your root moko directory, where $OMDIR points)

mkdir local local/conf local/classes local/packages local/packages/images local/packages/tasks -p

* Copy <code>site.conf</code> from the openmoko tree to <code>local/conf</code>

cp build/conf/site.conf local/conf/site.conf

* Edit the local/conf/site.conf you copied to add the new tree as a source for bitbake recipes.
{{Note | I had to edit the build/conf/site.conf file instead to avoid "no provider of build target" errors.
I'm guessing it's a problem with '''export BBPATH''' in a later step-[[User:Flerchjj|Flerchjj]]}}

Change the current <code>BBFILES</code> to look like this:
BBFILES := "${OMDIR}/openembedded/packages/*/*.bb ${OMDIR}/oe/packages/*/*.bb ${OMDIR}/local/packages/*/*.bb"
Change your <code>BBFILE_COLLECTIONS</code> line to look like this:
BBFILE_COLLECTIONS = "upstream local overlay"
Add this line:
BBFILE_PATTERN_overlay = "^${OMDIR}/local/"
Add this line:
BBFILE_PRIORITY_overlay = "20"

The <code>BBFILE_PRIORITY</code> should be greater than all the other <code>BBFILE_PRIORITY</code> variables on the same file.

Make sure there is a BBFILE_PRIORITY_* and a BBFILE_PATTERN_* for each name given in BBFILE_COLLECTIONS. For examle, if you only define the entries above, reduce BBFILE_COLLECTIONS to "overlay".

* Change your <code>BBPATH</code> environment variable to add the new tree ''before'' the two others in your <code>setup-env</code> file. Bitbake only seems to use the first site.conf file it finds. <code>setup-env</code> is created by [[MokoMakefile]] automatically and is located in your <code>${OMDIR}</code> directory.

export BBPATH="${OMDIR}/local:${OMDIR}/build:${OMDIR}/oe:${OMDIR}/openembedded"

== Using Your New Local Overlay ==

=== Changing files in conf/ ===

To change a file in conf/, just copy the file to the overlay tree (preserving the directory structure) and edit it.

=== Changing files in classes/ ===

To change a file in classes/, just copy the file to the overlay tree and edit it.

=== Changing packages ===

Changing a package's recipe is a bit more complex. You have to copy over (or symlink) not only the .bb file for the package, but also ''all'' the files it includes with <code>require</code>, and the <code>FILESDIR</code> directories (all directories referred to by <code>FILESDIR</code>, usually named either ''package''-''version'' or <code>files</code>). If you forget one of them, the build will give an error (either when parsing the recipe in the case of <code>require</code>, or when trying to build in the case of the <code>FILESDIR</code> directories).

=== Adding a new package ===

You can add a new package (or a recipe for a new version of a package) to the overlay tree simply by creating it on the overlay tree.

=== Creating your own images ===

To create you own images we'll use the base openmoko .bb files and modify them to suit. Where you see ''scaredycat'' replace this with something to identify your own images.

edit local/packages/images/scaredycat-openmoko-devel-image.bb and paste this:

<pre>
require scaredycat-openmoko-image.bb

IMAGE_INSTALL += "task-openmoko-debug"

</pre>

then edit local/packages/images/scaredycat-openmoko-image.bb

<pre>
#------------------------------------------------------
# OpenMoko Image Recipe
#------------------------------------------------------

export IMAGE_BASENAME = "${PN}"
export IMAGE_LINGUAS = ""

export IMAGE_INSTALL = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko-linux \
task-openmoko-net \
task-openmoko-ui \
task-openmoko-base \
task-openmoko-phone \
task-openmoko-games \
task-openmoko-pim \
task-openmoko-scaredycat \
"

inherit image

LICENSE = MIT

ROOTFS_POSTPROCESS_COMMAND += 'date "+%m%d%H%M%Y" >${IMAGE_ROOTFS}/etc/timestamp'

</pre>

edit local/packages/tasks/task-openmoko-scaredycat.bb - this is where we put the things we want to include in our image, above and beyond the standard image. This example includes '''[http://wiki.openmoko.org/wiki/Scummvm scummvm]''' and '''[http://www.handhelds.org/moin/moin.cgi/kbdd kbdd]'''. If you modify this file, make sure you update the '''PR''' by incrementing the number each time.

<pre>
DESCRIPTION = "OpenMoko: Scaredycat Additions"
SECTION = "openmoko/base"
LICENSE = "original"
PR = "r2"

inherit task

RDEPENDS_task-openmoko-scaredycat = "\
scummvm \
kbdd \
"

</pre>

==== Actually building your image ====

To build you image, which will be located with your other images, do the following:

# cd build ; . ../setup-env ; bitbake scaredycat-openmoko-devel-image

== Your First Application ==

I know that I said I'd have a GDK application in here, however, I'd really like to get this whole course done first and have you guys starting to code instead of just looking at what I've written!

This will be a very simple CLI hello world.

=== Before We Code ===

Like a good coder you want to make sure that you're not just doing things, but that you're doing them the right way!

Now change directories into your <code>local/packages</code> directory.The following commands expect you'll be in that directory so don't change unless you know what you're doing!

You'll want to make a directory with the name of your application, and a subdirectory called files.
mkdir myhelloworld myhelloworld/files
Now you'll want to create two files in the <code>files</code> directory
touch myhelloworld/files/README.txt myhelloworld/files/myhelloworld.c
And finally you'll want to create a bitbake file.
touch myhelloworld/myhelloworld.bb

Alrighty now all your necessary files are created so lets go over this real quick.
<pre>
$HOME
+- $OMDIR (contains the official openmoko tree)
| +- local/
| +- packages/
| +- myhelloworld/
| +- myhelloworld.bb
| +- files/
| +- myhelloworld.c
| +- README.txt
</pre>

That should be your structure, if it's not you should go and fix it up.
=== Filling the Files ===

So you've got your sample files all laid out now it's time to make them actually do something.

myhelloworld.c
<pre>
#include <stdio.h>

int main(int argc, char** argv)
{
printf("Ello Poppet!\n");
return 0;
}
</pre>

README.txt
<pre>
This is a command line application. It prints a simple Hello World! To stdout.
</pre>

myhelloworld.bb
<pre>
DESCRIPTION = "A killer hello world application"
AUTHOR = "Bryce Leo"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://myhelloworld.c \
file://README.txt "

S = "${WORKDIR}/myhelloworld/"

do_compile() {
${CC} ${CFLAGS} ${LDFLAGS} ${WORKDIR}/myhelloworld.c -o myhelloworld
}

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/myhelloworld
install -m 0755 ${S}/myhelloworld ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/myhelloworld
}

</pre>

=== Your First Compilation ===

This is where the [[MokoMakefile]] comes in very very handy. Change to your ${OMDIR} directory, You'll know it by the fact that it is where <code>Makefile</code> resides.
make build-package-myhelloworld

(make sure you run make openmoko-devel-image at least once before building your own packages)

This should all come back and not return any error messages, The output should end in something similar to
<pre>
NOTE: package myhelloworld-1.0: completed
NOTE: build 200707291926: completed
Build statistics:
Attempted builds: 1
</pre>

Now that no errors were thrown we are happily done!

== Adding Your Application to the Image ==

So you've had an idea, you've setup the build environment, you've setup your local overlay, you've laid out your application tree, you've put code into those fantastic files of yours and now it compiles.There's only one thing left to do. Add that application to your image.

Now lets go over in words and whys what we're about to do. First we need to make modify the <code>${OMDIR}/build/conf/local.conf</code>. We add in the variable <code>DISTRO_EXTRA_RDEPENDS</code> and set its value to include <code>myhelloworld</code>. If you'd like to include other packages from your own overlay or the OM tree just add them inseparated by spaces. After this gets added as a dependency to build the Distro (in this case OpenMoko). Now we have to re-build the task-base package. This essentially just generates an ipk file that will "Merge machine and distro options to create a basic machine task/package." It pretty much builds a file with a list of packages to be installed that are required for the distro to work correctly. So then you just go through and make <code>openmoko-devel-image, build-qemu, flash-qemu-local,</code> and <code>run-qemu</code>. Then calibrate your stylus, head over to the terminal, and run your application!

=== Modifying Your local.conf ===
Now, go into your build config directory <code>${OMDIR}/build/conf/</code> and now you'll be editing <code>local.conf</code>
Add this line to you <code>local.conf</code>
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
With this line you can also include other applications from the OE tree. For instance my <code>local.conf</code> looks like this.
<pre>
MACHINE = "fic-gta01"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS += "lua dillo myhelloworld"
</pre>

Now that you've fixed your <code>local.conf</code> it's time to go through all the necessary tasks to add and re-build you image and have your sweet package included.

=== Building ===
Now come the easy part thanks to [[MokoMakefile]].

make rebuild-package-task-base
make openmoko-devel-image
make build-qemu
make flash-qemu-local

Now all you have to do is run qemu.
make run-qemu

From here after you calibrate your stylus, you click on the Menu in the top right, click down to terminal, then just run your program.
<pre>
root@fic-gta02:/$ myhelloworld
Ello Poppet!
</pre>

==Adding Python scripts as applications==
This is for adding [[python]] scripts/packages to the image for your own use.
===First steps===
First, you need to modify the <code>local.conf</code> file as described above. You need to modify
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
to
DISTRO_EXTRA_RDEPENDS += "myhelloworld python"

--[[User:Xkr47|xkr47]] 18:21, 11 August 2007 (CEST) Hmm surely the new line should be DISTRO_EXTRA_RDEPENDS += "pyhelloworld python" instead since the package we create below is pyhelloworld..

This is because python is not included by default in the openmoko image. Or you can use <code>python-pygtk2</code> if you wish.

Next, you need to perform these actions from the <code>$OMDIR/local</code> directory.

mkdir packages/pyhelloworld packages/pyhelloworld/files

touch packages/pyhelloworld/files/pyhello packages/pyhelloworld/README.txt

touch packages/pyhelloworld/pyhelloworld.bb

===Filling in the files===
Now, edit <code>packages/pyhelloworld/files/pyhello</code> to contain:
<pre>
#!/usr/bin/python

print "hello world!"
print "shutting down now. Farewell oh cruel, cruel world!"
</pre>

Next up, is editing <code>packages/pyhelloworld/files/README.txt</code> to say:

This is the most awesome helloworld application ever. Know why? It has SNAKES!

Kidding aside, next is the all important <code> packages/pyhelloworld/pyhelloworld.bb:</code>
<pre>
DESCRIPTION = "A pythonic hello world application"
AUTHOR = "Tyler Laing"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://pyhello \
file://README.txt "

S = "${WORKDIR}/pyhelloworld/"

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/pyhelloworld
install -m 0755 ${WORKDIR}/pyhello ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/pyhelloworld
}

</pre>

I'll explain each of the parts right here, for future reference.

====Meanings of variables in .bb files====

$WORKDIR = $OMDIR/local/packages/<application directory>
$bindir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/bin
$docir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/share/doc
$D = $OMDIR/build/

====Final steps====
Complete the last steps as per the above instructions, from the point of altering <code>DISTRO_EXTRA_RDEPENDS</code>.

And you're done!

[[Category:Applications]]
[[Category:Openmoko]]
[[Category:Guides]]

@@ Line 1: / Line 1: @@
 == Was ist das Ziel? ==
@@ Line 354: / Line 356: @@
 And you're done!
-[[Category:Applications/de]]
+[[Category:Application Developer/de]]
-[[Category:Guides/de]]
+[[Category:System Developers/de]]

← Older revision		Revision as of 11:42, 7 September 2008
Line 355:		Line 355:

	[[Category:Applications/de]]		[[Category:Applications/de]]
−	~~[[Category:Openmoko/de]]~~
	[[Category:Guides/de]]		[[Category:Guides/de]]

@@ Line 3: / Line 3: @@
 Das Ziel dieser Seite ist es zu zeigen, wie man eine Anwendung die man programmiert hat (oder die Beispielanwendung) richtig in rootfs einbindet. Diese Seite ist ein bisschen die Summe verschiedener Artikel. Es werden Informationen bezogen aus [[MokoMakefile/de]], [[User:CesarB/Using a local overlay|Using a local overlay/de]], [[Building a hello world application/de]], and [[Create a package from existing sources/de]]. Wie man sehen kann ist das Ziel eine gründliche Einführung und führt von der Idee bis zur Einbindung der Anwendung.
-== Setting Up the Openmoko Environment ==
+== Einrichten einer Openmoko-Umgebung ==
 {| border="1" cellspacing="0" cellpadding="5"

@@ Line 1: / Line 1: @@
 == Was ist das Ziel? ==
-Das Ziel dieser Seite ist es zu zeigen, wie man eine Anwendung die man programmiert hat (oder die Beispielanwendung) richtig in rootfs einbindet. Diese Seite ist ein bisschen die Summe verschiedener Artikel. Es werden Informationen bezogen aus [[MokoMakefile/de]], [[User:CesarB/Using a local overlay|Using a local overlay/de]], [[Building a hello world application]], and [[Create a package from existing sources]]. Wie man sehen kann ist das Ziel eine gründliche Einführung und führt von der Idee bis zur Einbindung der Anwendung.
+Das Ziel dieser Seite ist es zu zeigen, wie man eine Anwendung die man programmiert hat (oder die Beispielanwendung) richtig in rootfs einbindet. Diese Seite ist ein bisschen die Summe verschiedener Artikel. Es werden Informationen bezogen aus [[MokoMakefile/de]], [[User:CesarB/Using a local overlay|Using a local overlay/de]], [[Building a hello world application/de]], and [[Create a package from existing sources/de]]. Wie man sehen kann ist das Ziel eine gründliche Einführung und führt von der Idee bis zur Einbindung der Anwendung.
 == Setting Up the Openmoko Environment ==

@@ Line 1: / Line 1: @@
 == Was ist das Ziel? ==
-Das Ziel dieser Seite ist es zu zeigen, wie man eine Anwendung die man programmiert hat (oder die Beispielanwendung) richtig in rootfs einbindet. Diese Seite ist ein bisschen die Summe verschiedener Artikel. Es werden Informationen bezogen aus [[MokoMakefile/de]], [[User:CesarB/Using a local overlay|Using a local overlay/de]], [[Building a hello world application/de]], and [[Create a package from existing sources/de]]. Wie man sehen kann ist das Ziel eine gründliche Einführung und führt von der Idee bis zur Einbindung der Anwendung.
+Das Ziel dieser Seite ist es zu zeigen, wie man eine Anwendung die man programmiert hat (oder die Beispielanwendung) richtig in rootfs einbindet. Diese Seite ist ein bisschen die Summe verschiedener Artikel. Es werden Informationen bezogen aus [[MokoMakefile/de]], [[User:CesarB/Using a local overlay|Using a local overlay/de]], [[Building a hello world application]], and [[Create a package from existing sources]]. Wie man sehen kann ist das Ziel eine gründliche Einführung und führt von der Idee bis zur Einbindung der Anwendung.
 == Setting Up the Openmoko Environment ==

@@ Line 354: / Line 354: @@
 And you're done!
-[[Category:Applications]]
+[[Category:Applications/de]]
-[[Category:Openmoko]]
+[[Category:Openmoko/de]]
-[[Category:Guides]]
+[[Category:Guides/de]]

@@ Line 11: / Line 11: @@
 |}
-This part of the tutorial is going to be pretty basic. I absolutely love [[MokoMakefile]] -- it's fantastic. The creator has done and continues to do a fantastic job with this. I see absolutely no reason not to use it. I put my OpenMoko development directory in /home/bryce/mokodev/ and it works great for me. You can feel free to do the same or put it anywhere else in your user directory (or anywhere on your system if you're feeling daring and a little nutty).
+This part of the tutorial is going to be pretty basic. I absolutely love [[MokoMakefile]] -- it's fantastic. The creator has done and continues to do a fantastic job with this. I see absolutely no reason not to use it. I put my Openmoko development directory in /home/bryce/mokodev/ and it works great for me. You can feel free to do the same or put it anywhere else in your user directory (or anywhere on your system if you're feeling daring and a little nutty).
 To get your environment set up, please get it set up according to [[MokoMakefile]]. However, if you do have the build environment set up manually and you're sure you know what you're doing, then feel free to go forward with this.
 == Setting Up a Local Overlay ==
-If you're at the point of setting up a local overlay, this means a couple things. First: you've had a brilliant idea for an application that you just need to have on the OpenMoko platform. Second: you realize that this killer app of yours needs to be done properly and you're not going to do anything silly like include it in the actual tree for the OpenMoko distro because it would probably end up just getting overwritten eventually, or you just realize that it's bad practice!
+If you're at the point of setting up a local overlay, this means a couple things. First: you've had a brilliant idea for an application that you just need to have on the Openmoko platform. Second: you realize that this killer app of yours needs to be done properly and you're not going to do anything silly like include it in the actual tree for the Openmoko distro because it would probably end up just getting overwritten eventually, or you just realize that it's bad practice!
-If you're wondering why and what a local overlay is then let me take this time to explain it to you. A local overlay is where you, as a developer, keep your local files in an OE style setup so that you can simply pull your updated code into the tree. You add your overlay tree into the bitbake setup so that when you call bitbake it will pull your own or your customized packages before going to the OE or OpenMoko trees. This keeps everything nice and organized for you and also allows you to build/rebuild/include your apps by using the [[MokoMakefile]]
+If you're wondering why and what a local overlay is then let me take this time to explain it to you. A local overlay is where you, as a developer, keep your local files in an OE style setup so that you can simply pull your updated code into the tree. You add your overlay tree into the bitbake setup so that when you call bitbake it will pull your own or your customized packages before going to the OE or Openmoko trees. This keeps everything nice and organized for you and also allows you to build/rebuild/include your apps by using the [[MokoMakefile]]
 Thank you to [[User:CesarB]] for this part of the wiki.
@@ Line 88: / Line 88: @@
 <pre>
 #------------------------------------------------------
-# OpenMoko Image Recipe
+# Openmoko Image Recipe
 #------------------------------------------------------
@@ Line 118: / Line 118: @@
 <pre>
-DESCRIPTION = "OpenMoko: Scaredycat Additions"
+DESCRIPTION = "Openmoko: Scaredycat Additions"
 SECTION = "openmoko/base"
 LICENSE = "original"
@@ Line 244: / Line 244: @@
 So you've had an idea, you've setup the build environment, you've setup your local overlay, you've laid out your application tree, you've put code into those fantastic files of yours and now it compiles.There's only one thing left to do. Add that application to your image.
-Now lets go over in words and whys what we're about to do. First we need to make modify the <code>${OMDIR}/build/conf/local.conf</code>. We add in the variable <code>DISTRO_EXTRA_RDEPENDS</code> and set its value to include <code>myhelloworld</code>. If you'd like to include other packages from your own overlay or the OM tree just add them inseparated by spaces. After this gets added as a dependency to build the Distro (in this case OpenMoko). Now we have to re-build the task-base package. This essentially just generates an ipk file that will "Merge machine and distro options to create a basic machine task/package." It pretty much builds a file with a list of packages to be installed that are required for the distro to work correctly. So then you just go through and make <code>openmoko-devel-image, build-qemu, flash-qemu-local,</code> and <code>run-qemu</code>. Then calibrate your stylus, head over to the terminal, and run your application!
+Now lets go over in words and whys what we're about to do. First we need to make modify the <code>${OMDIR}/build/conf/local.conf</code>. We add in the variable <code>DISTRO_EXTRA_RDEPENDS</code> and set its value to include <code>myhelloworld</code>. If you'd like to include other packages from your own overlay or the OM tree just add them inseparated by spaces. After this gets added as a dependency to build the Distro (in this case Openmoko). Now we have to re-build the task-base package. This essentially just generates an ipk file that will "Merge machine and distro options to create a basic machine task/package." It pretty much builds a file with a list of packages to be installed that are required for the distro to work correctly. So then you just go through and make <code>openmoko-devel-image, build-qemu, flash-qemu-local,</code> and <code>run-qemu</code>. Then calibrate your stylus, head over to the terminal, and run your application!
 === Modifying Your local.conf ===