1
0
mirror of https://git.yoctoproject.org/poky synced 2026-06-02 01:19:52 +00:00

bitbake: bitbake-user-manual-hello.xml: Edits to the "Hello World" Appendix.

Fixes [YOCTO #1973]

These are review changes applied from Paul Eggleton.

(Bitbake rev: fe083b674b20b254877a6d8249b11c9a7373866e)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2014-04-17 11:57:51 -07:00
committed by Richard Purdie
parent 78217d37d2
commit 33dfe60c35
@@ -14,7 +14,7 @@
example. example.
This appendix demonstrates, in tutorial form, Hello This appendix demonstrates, in tutorial form, Hello
World within the context of BitBake. World within the context of BitBake.
The tutorial describes how to create a new Project The tutorial describes how to create a new project
and the applicable metadata files necessary to allow and the applicable metadata files necessary to allow
BitBake to build it. BitBake to build it.
</para> </para>
@@ -95,26 +95,6 @@
You should now be able to enter the <filename>bitbake</filename> You should now be able to enter the <filename>bitbake</filename>
command from the command line while working from any directory. command from the command line while working from any directory.
</para> </para>
<para>
For a more permanent solution, assuming you are running the BASH
shell, edit <filename>~/.bashrc</filename> and add the following to the end
of that file:
<literallayout class='monospaced'>
PATH=&lt;path-to-bitbake-executable&gt;:$PATH
</literallayout>
</para>
<para>
If you're a Vim user, you will find useful
Vim configuration contributions in the
<filename>contrib/vim</filename> directory.
Copy the files from that directory to your
<filename>/home/yourusername/.vim</filename>
directory.
If that directory does not exist, create it, and then
restart Vim.
</para>
</section> </section>
<section id='the-hello-world-example'> <section id='the-hello-world-example'>
@@ -503,14 +483,22 @@ ERROR: Unable to parse base: ParseError in configuration INHERITs: Could not inh
BitBake finds the <filename>printhello</filename> recipe and BitBake finds the <filename>printhello</filename> recipe and
successfully runs the task. successfully runs the task.
<note> <note>
Rerunning the task without removing the <filename>tmp</filename> After the first execution, re-running
directory will not result in a BitBake run that prints the <filename>bitbake printhello</filename> again will not
same console output. result in a BitBake run that prints the same console
BitBake uses its Setscene process and determines that output.
nothing needs to be re-run. The reason for this is that the first time the
If you delete the <filename>tmp</filename> directory and <filename>printhello.bb</filename> recipe's
then re-run the build, the printed output appears <filename>do_build</filename> task executes
at the console. successfully, BitBake writes a stamp file for the task.
Thus, the next time you attempt to run the task
using that same <filename>bitbake</filename> command,
BitBake notices the stamp and therefore determines
that the task does not need to be re-run.
If you delete the <filename>tmp</filename> directory
or run <filename>bitbake -c clean printhello</filename>
and then re-run the build, the "Hello, World!" message will
be printed again.
</note> </note>
</para></listitem> </para></listitem>
</orderedlist> </orderedlist>