From fe083b674b20b254877a6d8249b11c9a7373866e Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 17 Apr 2014 11:57:51 -0700 Subject: bitbake-user-manual-hello.xml: Edits to the "Hello World" Appendix. Fixes [YOCTO #1973] These are review changes applied from Paul Eggleton. Signed-off-by: Scott Rifenbark --- .../bitbake-user-manual-hello.xml | 46 ++++++++-------------- 1 file changed, 17 insertions(+), 29 deletions(-) diff --git a/doc/bitbake-user-manual/bitbake-user-manual-hello.xml b/doc/bitbake-user-manual/bitbake-user-manual-hello.xml index 2d67ff77d..4ce7ed9f8 100644 --- a/doc/bitbake-user-manual/bitbake-user-manual-hello.xml +++ b/doc/bitbake-user-manual/bitbake-user-manual-hello.xml @@ -14,7 +14,7 @@ example. This appendix demonstrates, in tutorial form, Hello 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 BitBake to build it. @@ -95,26 +95,6 @@ You should now be able to enter the bitbake command from the command line while working from any directory. - - - For a more permanent solution, assuming you are running the BASH - shell, edit ~/.bashrc and add the following to the end - of that file: - - PATH=<path-to-bitbake-executable>:$PATH - - - - - If you're a Vim user, you will find useful - Vim configuration contributions in the - contrib/vim directory. - Copy the files from that directory to your - /home/yourusername/.vim - directory. - If that directory does not exist, create it, and then - restart Vim. -
@@ -503,14 +483,22 @@ ERROR: Unable to parse base: ParseError in configuration INHERITs: Could not inh BitBake finds the printhello recipe and successfully runs the task. - Rerunning the task without removing the tmp - directory will not result in a BitBake run that prints the - same console output. - BitBake uses its Setscene process and determines that - nothing needs to be re-run. - If you delete the tmp directory and - then re-run the build, the printed output appears - at the console. + After the first execution, re-running + bitbake printhello again will not + result in a BitBake run that prints the same console + output. + The reason for this is that the first time the + printhello.bb recipe's + do_build task executes + successfully, BitBake writes a stamp file for the task. + Thus, the next time you attempt to run the task + using that same bitbake command, + BitBake notices the stamp and therefore determines + that the task does not need to be re-run. + If you delete the tmp directory + or run bitbake -c clean printhello + and then re-run the build, the "Hello, World!" message will + be printed again. -- cgit 1.2.3-korg