summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--bitbake/doc/bitbake-user-manual/bitbake-user-manual-hello.xml46
1 files changed, 17 insertions, 29 deletions
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-hello.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-hello.xml
index 2d67ff77da..4ce7ed9f8c 100644
--- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-hello.xml
+++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-hello.xml
@@ -14,7 +14,7 @@
14 example. 14 example.
15 This appendix demonstrates, in tutorial form, Hello 15 This appendix demonstrates, in tutorial form, Hello
16 World within the context of BitBake. 16 World within the context of BitBake.
17 The tutorial describes how to create a new Project 17 The tutorial describes how to create a new project
18 and the applicable metadata files necessary to allow 18 and the applicable metadata files necessary to allow
19 BitBake to build it. 19 BitBake to build it.
20 </para> 20 </para>
@@ -95,26 +95,6 @@
95 You should now be able to enter the <filename>bitbake</filename> 95 You should now be able to enter the <filename>bitbake</filename>
96 command from the command line while working from any directory. 96 command from the command line while working from any directory.
97 </para> 97 </para>
98
99 <para>
100 For a more permanent solution, assuming you are running the BASH
101 shell, edit <filename>~/.bashrc</filename> and add the following to the end
102 of that file:
103 <literallayout class='monospaced'>
104 PATH=&lt;path-to-bitbake-executable&gt;:$PATH
105 </literallayout>
106 </para>
107
108 <para>
109 If you're a Vim user, you will find useful
110 Vim configuration contributions in the
111 <filename>contrib/vim</filename> directory.
112 Copy the files from that directory to your
113 <filename>/home/yourusername/.vim</filename>
114 directory.
115 If that directory does not exist, create it, and then
116 restart Vim.
117 </para>
118 </section> 98 </section>
119 99
120 <section id='the-hello-world-example'> 100 <section id='the-hello-world-example'>
@@ -503,14 +483,22 @@ ERROR: Unable to parse base: ParseError in configuration INHERITs: Could not inh
503 BitBake finds the <filename>printhello</filename> recipe and 483 BitBake finds the <filename>printhello</filename> recipe and
504 successfully runs the task. 484 successfully runs the task.
505 <note> 485 <note>
506 Rerunning the task without removing the <filename>tmp</filename> 486 After the first execution, re-running
507 directory will not result in a BitBake run that prints the 487 <filename>bitbake printhello</filename> again will not
508 same console output. 488 result in a BitBake run that prints the same console
509 BitBake uses its Setscene process and determines that 489 output.
510 nothing needs to be re-run. 490 The reason for this is that the first time the
511 If you delete the <filename>tmp</filename> directory and 491 <filename>printhello.bb</filename> recipe's
512 then re-run the build, the printed output appears 492 <filename>do_build</filename> task executes
513 at the console. 493 successfully, BitBake writes a stamp file for the task.
494 Thus, the next time you attempt to run the task
495 using that same <filename>bitbake</filename> command,
496 BitBake notices the stamp and therefore determines
497 that the task does not need to be re-run.
498 If you delete the <filename>tmp</filename> directory
499 or run <filename>bitbake -c clean printhello</filename>
500 and then re-run the build, the "Hello, World!" message will
501 be printed again.
514 </note> 502 </note>
515 </para></listitem> 503 </para></listitem>
516 </orderedlist> 504 </orderedlist>