From c3cd6731d701dac1d41fc28495db4d61216d7807 Mon Sep 17 00:00:00 2001 From: Chase Maupin Date: Wed, 26 May 2010 03:09:29 +0000 Subject: docs/common_use_cases: Fix documentation errors * Fixed up typos and other errors in the documentation. Acked-by: Koen Kooi Signed-off-by: Chase Maupin Signed-off-by: Denys Dmytriyenko --- docs/usermanual/chapters/common_use_cases.xml | 45 ++++++++++++++------------- 1 file changed, 24 insertions(+), 21 deletions(-) diff --git a/docs/usermanual/chapters/common_use_cases.xml b/docs/usermanual/chapters/common_use_cases.xml index 7ae3ee5ada..d86d0ca8d1 100644 --- a/docs/usermanual/chapters/common_use_cases.xml +++ b/docs/usermanual/chapters/common_use_cases.xml @@ -7,11 +7,12 @@ Creating a new distribution is not complicated, however we urge you to try existing distributions first, because it's also very easy to do - wrong. The config need to be created in /conf/distro directory. So what - has to be inside? + wrong. The config needs to be created in $OEBASE/openembedded/conf/distro + directory. So what has to be inside? + DISTRO_VERSION so users will know which - version of distribution they use. + version of the distribution they are using. @@ -71,29 +72,30 @@ SRCDATE = "20061014"
Adding a new Machine - To be able to build for device OpenEmbedded have to know it, so - machine config file need to be written. All those configs are stored in - /conf/machine/ directory. + To be able to build for a device OpenEmbedded has to know about it, + so a machine config file needs to be written. All of the machine + configs are stored in $OEBASE/openembedded/conf/machine/ directory. As usual some variables are required: - TARGET_ARCH which describe which CPU - architecture does machine use. + TARGET_ARCH describes which CPU + architecture the machine uses. - MACHINE_FEATURES which describe which - features device has. More about it in MACHINE_FEATURES which describes which + features the device has. More about it in task-base section. PREFERRED_PROVIDER_virtual/kernel has to - point into proper kernel recipe for this machine. + point to the proper kernel recipe for this machine. - Next kernel recipe needs to be added. + Next the kernel recipe needs to be added if it doesn't already exist. +
@@ -105,7 +107,7 @@ SRCDATE = "20061014"
building from unstable source code Building against the latest, bleeding-edge source has some intricacies of its own. - For one, it is desirable to pin down a 1 code revision that is known to build to + For one, it is desirable to pin down a code revision that is known to build to prevent random breakage in OE at the most inopportune time for all OE users. Here is how to do that properly. @@ -113,7 +115,8 @@ SRCDATE = "20061014" for cvs: add 'PV = "1.1+cvs${SRCREV}"' to your bb file. Accompany either with an entry to conf/distro/include/sane-srcrevs.inc for a revision that you know - builds successfully. + builds successfully. It is also common to define the stable SRCREV + for your package directly in the package recipe. If you really absolutely have to follow the latest commits, you can do that by adding @@ -126,7 +129,7 @@ SRCDATE = "20061014"
Creating your own image - Creating own image is easy - only few variables needs to be set: + Creating own image is easy - only few variables need to be set: IMAGE_BASENAME to give a name for your own @@ -147,7 +150,7 @@ SRCDATE = "20061014" IMAGE_LINGUAS is an optional list of languages which has to be installed into the image - Then adding of the image class use: + Then add the image class using: inherit image And the image recipe is ready for usage. @@ -240,7 +243,7 @@ export LOCALDIR=$PWD/secret-isv Use source build_source to source the script, - use env to check that the variable where + use env to check that the variables were exported.
@@ -484,8 +487,8 @@ RDEPENDS_${PN} += "\ Putting it together In the previous two sections we have prepared the host and target side. One thing that is missing is combining the two newly - created tasks and actually create the SDK. This is what we are going - to do now. + created tasks and actually creating the SDK. This is what we are + going to do now. Create meta-toolchain-YOU.bb in the recipes/meta directory and place the following @@ -529,7 +532,7 @@ SDK_SUFFIX = "toolchain-YOUR" optional dependencies like directFB, glib-2.0, gstreamer-0.10, tslib and more esoteric dependencies like mysql and postgres. This allows developers to simply start developing using Qt and enables system - integrator to easily recompile Qt and base libraries without tracking + integrators to easily recompile Qt and base libraries without tracking down extra dependencies. @@ -575,7 +578,7 @@ $ bitbake meta-toolchain-qte should start by downloading the SDK and untar it to the root folder (/). Once this operation is finished you will find a new directory /usr/local/angstrom/arm/ and - it contains the environment-setup to setup the + it contains the environment-setup file to setup the QMAKESPEC and various other paths. -- cgit 1.2.3-korg