linux/poky.git/documentation/ref-manual/usingpoky.xml, branch 1.7_M1

dev-manual, kernel-dev, ref-manual: Updated task name usage.

2014-06-18T09:30:48+00:00

There was inconsistency on how we refer to a task name throughout the YP manual set. The proper way is "do_". Some occurrences did not include the "do_" prefix. These have been fixed. (From yocto-docs rev: b32821bb0d3e6de7bca68b25c662a023526a10c4) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

ref-manual: Added links to new do_* sections.

2014-05-13T06:50:58+00:00

With the creation of the new chapter that documents the 51 tasks defined by the OpenEmbedded build system, the remainder of the ref-manual had many first-instance occurrences of do_* task names that could be cross-referenced to the new sections. I have added these links. (From yocto-docs rev: 2ff39bd226a1d8f11924283bbaa3542a9d936ba3) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

ref-manual: Edits to the "Using" chapter.

2014-03-30T09:18:38+00:00

Along with some minor things I did the following: * Added a brief explanation and reference to the reporting error tool. It seemed like a good chapter to include it. I put it in the debugging section. * I added a pointer to the BitBake manual right at the top of a section that had many usages of the bitbake command. (From yocto-docs rev: 9317433bc715e9fdac2fc629ed659ac926d67531) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

ref-manual: Edits to "Running Specific Tasks"

2014-03-25T12:29:44+00:00

Paul Eggleton noted that the output to bitbake -c listtasks was documented as going to a specific file only when in fact it also goes to the console. I updated the section to include that fact. (From yocto-docs rev: 0ed7da3f0fc21412c1045889f241a3d86587d16f) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

ref-manual: Edits to "Understanding What the Build History Contains" section.

2014-03-25T12:29:37+00:00

The opening sentence here said that the build history is kept in the $TMPDIR/buildhistory directory in the Build Directory as defined by the BUILDHISTORY_DIR variable. Well, the variable claims it is kept in $TOPDIR/buildhistory. I went with the variable as the correct source. So, I changed the intro sentence here. Reported-by: Laszlo Papp (From yocto-docs rev: 242e372affe771776bdfc17f3e3f5187d8965467) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

ref-manual: Edits to the "Maintaining Build Output Quality" section.

2014-03-25T12:29:37+00:00

Removed the bit about isolating SDK information. Also removed the workaround and text regarding the limitation that caused adding and removing INHERIT += "buildhistory" to re-execute tasks. Added a few links to some newly documented variables. (From yocto-docs rev: 7d13bea6d9f0c2bdc9aa58c2933998d6d10ac810) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

ref-manual: Updates to "Maintaining Build Output Quality"

2014-03-25T12:29:37+00:00

I modified a few areas to help integrate some newly documented BUILDHISTORY_* variables. Mostly some rewriting to feature some variables that help the user select build history features. (From yocto-docs rev: 8cb6a09ba7f0bd645a12e6f7a93247a9f0e77980) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

ref-manual: Changed depends.dot filename to pn-depends.dot.

2013-12-03T12:53:16+00:00

Reported-by: Robert P. J. Day (From yocto-docs rev: bd9f4ab6bd54a6d0edff1f5cfb6ea4d46f5bc9f1) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

ref-manual: Added the pn-buildlist file to list of files

2013-12-03T12:53:16+00:00

In the "Dependency Graphs" section, the pn-buildlist file was not mentioned as a file generated by the 'bitbake -g ' command. I added this in and provided a bit of re-writing. Reported-by: Robert P. J. Day (From yocto-docs rev: 435de6a980bd182e8033319e479ded1414e93eed) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

ref-manual: Cleaned up some instances of the term "working directory"

2013-12-03T12:53:15+00:00

This term should always reference a users current working directory and not be confused with the OpenEmbedded build system's "work directory (WORKDIR). I found several instances where the term "working directory" was not used correctly and fixed them. Reported-by: Robert P. J. Day (From yocto-docs rev: 300c78c1d54b2a4fbb8ecca03faa7c8c67bdc54f) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie