From 154a69bf190d281eafdb2244d3368cc505510125 Mon Sep 17 00:00:00 2001 From: Holger Hans Peter Freyther Date: Tue, 11 Aug 2009 14:15:09 +0200 Subject: usermanual: First round of spell checking --- docs/usermanual/chapters/common_use_cases.xml | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) (limited to 'docs') diff --git a/docs/usermanual/chapters/common_use_cases.xml b/docs/usermanual/chapters/common_use_cases.xml index b5d376a9db..7ae3ee5ada 100644 --- a/docs/usermanual/chapters/common_use_cases.xml +++ b/docs/usermanual/chapters/common_use_cases.xml @@ -105,7 +105,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 souce code revision that is known to build to + For one, it is desirable to pin down a 1 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. @@ -221,7 +221,7 @@ qt2 available.
- Sourcable script + Sourceable script To ease the usage of OpenEmbedded we start by creating a source-able script. This is actually a small variation from the @@ -381,7 +381,7 @@ NOTE: Couldn't find shared library provider for libm.so.6 OpenEmbedded tries to automatically add run-time dependencies (RDEPENDS) to generated packages. It is inspecting binaries and libraries and uses the shlibs - system to do add dependencies for the linked libaries, + system to do add dependencies for the linked libraries, however in this case it was not able to find packages providing these libraries as they were prebuilt. @@ -410,7 +410,7 @@ ASSUME_SHLIBS = "libqtopia2.so.2:qtopia2_2.4 libc.so.6:libc" What is provided by a SDK The Software Development Kit (SDK) should be easy to install and - enable your userbase to create binaries and libraries that work on the + enable your user-base to create binaries and libraries that work on the target hardware. @@ -452,10 +452,10 @@ RDEPENDS_${PN} += "YOUR-DEPENDENCY-sdk"
- Preapring the target side + Preparing the target side Your SDK should provide your user with header files and libraries he will need when doing application development. In OpenEmbedded the - ${PN}-dev isi providing the header files, pkg-config + ${PN}-dev is providing the header files, pkg-config files and symbolic links to libraries to allow using the library. The SDK should install these development packages to the SDK. @@ -506,7 +506,7 @@ SDK_SUFFIX = "toolchain-YOUR" directory inside your deploy directory with a SDK waiting for you. With the above command you still need to have OE configured with your conf/local.conf to select the machine and - distribution you are targetting. + distribution you are targeting. SDK creation currently does not work with the DISTRO @@ -526,11 +526,11 @@ SDK_SUFFIX = "toolchain-YOUR" Creating the SDK The SDK should contain a build of Qt Embedded, but also - optional depedencies like directFB, glib-2.0, gstreamer-0.10, tslib - and more esoteric depedencies like mysql and postgres. This allows + 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 - integrators to easily recompile Qt and base libraries without tracking - down extra depedencies. + integrator to easily recompile Qt and base libraries without tracking + down extra dependencies. OpenEmbedded provides an easy way to create a Qt Embedded -- cgit 1.2.3-korg