From 54956b8d506e42653d893764d5df27f1ce52a8be Mon Sep 17 00:00:00 2001 From: "Robert P. J. Day" Date: Wed, 2 Nov 2011 13:05:20 -0700 Subject: documentation/dev-manual/dev-manual-start.xml: Robert P. J. Edits Robert isolated a few technical errors and made some other wording suggestions. I took the technical corrections and modified one of his suggested wording changes. (From yocto-docs rev: 3c6bbae05cdf2265e04d967050354ce75d62b4e2) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-start.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'documentation') diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml index a5f3652..e9342d0 100644 --- a/documentation/dev-manual/dev-manual-start.xml +++ b/documentation/dev-manual/dev-manual-start.xml @@ -36,7 +36,7 @@ While the Yocto Project does not provide a strict testing framework, it does provide or generate for you artifacts that let you perform target-level and emulated testing and debugging. - And, if you are an Eclipse + Additionally, if you are an Eclipse IDE user, you can install an Eclipse Yocto Plug-in to allow you to develop within that familiar environment. @@ -77,7 +77,7 @@ Once you have the tarball, just extract it into a directory of your choice. For example, the following command extracts the Yocto Project 1.1 release tarball into the current working directory and sets up the Yocto Project file structure - with a top-level directory named poky-1.1: + with a top-level directory named poky-edison-6.0: $ tar xfj poky-edison-6.0.tar.bz2 @@ -195,7 +195,7 @@ meta-intel Git repository inside the poky Git repository. - $cd poky + $ cd poky $ git clone git://git.yoctoproject.org/meta-intel.git Initialized empty Git repository in /home/scottrif/poky/meta-intel/.git/ remote: Counting objects: 1325, done. @@ -240,7 +240,7 @@ Optionally ensure the conf/local.conf configuration file is set up how you want it. This file defines the target machine architecture and other build options. - Build the image using the BitBake command. + Build the image using the bitbake command. If you want information on Bitbake, see the user manual at . Run the image either on the actual hardware or using the QEMU -- cgit v1.1