aboutsummaryrefslogtreecommitdiffstats
path: root/README.md
diff options
context:
space:
mode:
authorwminer <wminer@linuxfoundation.org>2015-11-04 08:02:17 -0600
committerwminer <wminer@linuxfoundation.org>2015-11-04 08:02:17 -0600
commitd58321651ddaa20dd9876a51031a5de08e654f93 (patch)
tree91fd3ecf8ea83b4e4593deb036b5acc9e7ceb078 /README.md
parent0ef8a183969cc9c3c51feb7dca5025e5773840f5 (diff)
Added weston instructions and fixed some typos.
Change-Id: I56f9b68b722bf7abf784991517a2fc34f7b21902 Signed-off-by: wminer <wminer@linuxfoundation.org>
Diffstat (limited to 'README.md')
-rw-r--r--README.md19
1 files changed, 14 insertions, 5 deletions
diff --git a/README.md b/README.md
index 4b97f7427..8c4ce30b8 100644
--- a/README.md
+++ b/README.md
@@ -72,18 +72,18 @@ These packagegroups contains packages for application framework of AGL Distro.
Subsystem should maintain ``packagegroup-agl-appfw-[subsystem].bb`` which
should hold sufficient packages for application framework of AGL Distro.
-Subsystems also can maintain thier own packagegroups under appropriate
+Subsystems also can maintain their own packagegroups under appropriate
``recipes-*/``.
For example, Qt5 has 2 packagegroups in ``meta-agl-demo``,
-``packagegroup-agl-appfw-native-qt5`` and ``pacakgegroup-agl-demo-qt-examples``
+``packagegroup-agl-appfw-native-qt5`` and ``packagegroup-agl-demo-qt-examples``
which are under ``recipes-qt/``.
The ``packagegroup-agl-appfw-native-qt5`` is included by
-``pacakgegroup-agl-appfw-native`` because Qt5 belongs to native application
+``packagegroup-agl-appfw-native`` because Qt5 belongs to native application
framework of AGL Distro.
-The ``pacakgegroup-agl-demo-qt-examples`` is added to local.conf if needed
+The ``packagegroup-agl-demo-qt-examples`` is added to local.conf if needed
because they are not mandatory for AGL application framework and AGL Demo
Platform.
@@ -151,7 +151,15 @@ You can build a QEMU image using the following steps:
2. Build the full image of AGL Demo Platform and applications
$ bitbake agl-demo-platform
-3. Run the emulator. The path for the emulator (runqemu) was added during the envsetup.
+3. The Weston IVI-Shell always gets built ; it will not be started, however, unless you specify the following in your "conf/local.conf" file :
+
+IMAGE_INSTALL_append = " \
+ weston-ivi-shell-config \
+ "
+
+or you manually overwrites the "/etc/xdg/weston/weston.ini" file with a correct one.
+
+4. Run the emulator. The path for the emulator (runqemu) was added during the envsetup.
$ cd tmp/deploy/images/qemex86-64
$ runqemu bzImage-qemux86-64.bin agl-demo-platform-qemux86-64.ext3
@@ -161,6 +169,7 @@ You can build a QEMU image using the following steps:
5. Some weston samples are available from weston terminal.
+
Build a R-Car M2 (porter) image
-------------------------------