diff options
| author | Robert P. J. Day <rpjday@crashcourse.ca> | 2009-11-03 23:01:11 +0000 |
|---|---|---|
| committer | Holger Hans Peter Freyther <zecke@selfish.org> | 2009-11-05 10:24:18 +0100 |
| commit | aa6bc115054acc2507119086ebfc7995873c67ca (patch) | |
| tree | fd64b621cfaed368f5754bf0612eb3d0c93150f1 /docs | |
| parent | 810df5f14cb2f87371787ba3a935b6e7dec11570 (diff) | |
User manual typoes and aesthetics, chapter 2 only.
Some minor cleanups for Chapter 2 of the User Manual:
* add some DocBook tags for filenames
* update BitBake version to 1.8.16
* add missing space after "wget" command
* correct misspelled "local/conf" to "local.conf"
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Holger Hans Peter Freyther <zecke@selfish.org>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/usermanual/chapters/getting_oe.xml | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/docs/usermanual/chapters/getting_oe.xml b/docs/usermanual/chapters/getting_oe.xml index e8d1f2cc9d..8d9c5b7a0a 100644 --- a/docs/usermanual/chapters/getting_oe.xml +++ b/docs/usermanual/chapters/getting_oe.xml @@ -30,9 +30,9 @@ $ <command>cd</command> $OEBASE</screen> you to build your applications and images. </para> - <para>The <varname>$OEBASE</varname> will also contain both bitbake/ and - openembedded/ directories. These will be discussed in - <xref linkend="gettingoe_getting_bitbake"/> and + <para>The <varname>$OEBASE</varname> will also contain both of the + <literal>bitbake/<literal> and <literal>openembedded/</literal> directories. + These will be discussed in <xref linkend="gettingoe_getting_bitbake"/> and <xref linkend="gettingoe_getting_oe"/>. </para> </section> @@ -47,19 +47,19 @@ $ <command>cd</command> $OEBASE</screen> directory of <literal>openembedded/</literal> and <literal>build/</literal> directories. Indeed, as bitbake is written in python it does not need compilation for being used. You'll just have to - set the PATH variable so that the BitBake tools are accessible (see - <xref linkend="gettingoe_configuring_oe"/>).</para> + set the <varname>PATH</varname> variable so that the BitBake tools are + accessible (see <xref linkend="gettingoe_configuring_oe"/>).</para> <section><title>Downloading a <application>BitBake</application> release</title> <para>Releases are available from the berlios project website. The current release series is <application>BitBake</application> <emphasis>1.8</emphasis> - and the current release is <emphasis>1.8.12</emphasis>. To download execute + and the current release is <emphasis>1.8.16</emphasis>. To download execute the following commands: <screen> $ <command>cd</command> $OEBASE -$ <command>wget</command>http://download.berlios.de/bitbake/bitbake-1.8.12.tar.gz -$ <command>tar</command> -xvzf bitbake-1.8.12.tar.gz -$ <command>mv</command> bitbake-1.8.12 bitbake +$ <command>wget</command> http://download.berlios.de/bitbake/bitbake-1.8.16.tar.gz +$ <command>tar</command> -xvzf bitbake-1.8.16.tar.gz +$ <command>mv</command> bitbake-1.8.16 bitbake </screen> </para> @@ -270,7 +270,7 @@ MACHINE = "om-gta01"</screen> BitBake file is a logical unit of tasks to be executed. Normally this is a package to be built. Inter-recipe dependencies are obeyed. The recipes are located by BitBake via the <varname>BBFILES</varname> variable (set - in your <filename>$OEBASE/build/conf/local/conf</filename>), which is a + in your <filename>$OEBASE/build/conf/local.conf</filename>), which is a space separated list of <filename>.bb</filename> files, and does handle wildcards. </para> |