linux/poky.git/documentation, branch 1.2_M3

documentation/yocto-project-qs/yocto-project-qs.xml: removed disable dash text

2012-01-06T12:13:13+00:00

Richard made a concerted effort to enable Dash usage in Poky and the sanity check to detect it is no longer present. We should update the documentation to reflect this development. Specifically the section in the quickstart: "If your distribution is Ubuntu, you need to be running the bash shell. You can be sure you are running this shell by entering the following command and selecting "No" at the prompt: $ sudo dpkg-reconfigure dash " Is no longer required. I have removed it. Fixes [YOCTO #1820] Reported-by: Joshua Lock (From yocto-docs rev: 189a80571bb7a1afd53171d93273e7cc26460d63) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation/yocto-project-qs/yocto-project-qs.xml: Added libxml-parser-perl pkg

2012-01-06T12:13:12+00:00

A missing dependency surfaced during a build by community member Marc Ferland on a Ubuntu system. The "shared-mime-info" package would not build. Fix was to add the "libxml-parser-perl" package. So I added this package as a requirement for the Ubuntu systems. Reported-by: Marc Ferland (From yocto-docs rev: 3922f2eb24f8f2089c6fdb48a88530af2b26f159) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation/poky-ref-manual/ref-variables.xml: image size glossary

2012-01-06T12:13:12+00:00

I added three new glossary entries for how the build process figures out the image size. Entries are for IMAGE_ROOTFS_SIZE, IMAGE_OVERHEAD_FACTOR, and IMAGE_ROOTFS_EXTRA_SPACE. I still need to create a usage section for this topic. Likely this will be in the development manual in a new chapter I am thinking about. Fixes [YOCTO #1110] partially. (From yocto-docs rev: ec6b9d77d10a95f0a2d460dca3cf8eab5dfbf0c0) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation/poky-ref-manual: Enabling recipes with commercial license requirements

2012-01-06T12:13:12+00:00

I created a new section in the "Technical Details" chapter of the YP Reference Manual to deal with licensing. I migrated the existing section on tracking licenses from the "Extending YP" chapter into this section. The new section now includes that info as well as the new information here. Fixes [YOCTO #576] (From yocto-docs rev: b0d04bf99838d64e71ccd43d587d6641aaa26038) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation/kernel-manual/kernel-how-to.xml: general edits

2012-01-06T12:13:12+00:00

Some general edits up to section 3.4. (From yocto-docs rev: 5bcd22b6372017c4f78b18035193879890ed8244) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation/kernel-manual/kernel-concepts.xml: General edits.

2012-01-06T12:13:11+00:00

Cleaned up some areas. Fixed use of "uprev" term for consistency. (From yocto-docs rev: 2d0c4d3c28a218f6302aee8ff2841420fbde410d) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation/kernel-manual/kernel-doc-intro.xml: General clean-up

2012-01-06T12:13:11+00:00

(From yocto-docs rev: bab78b907279fcd9fd5c65a53c31ee1e51cd6576) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation/poky-ref-manual/technical-details.xml: edits per Richard Purdie

2011-12-16T16:58:41+00:00

Richard reviewed the new sections and had a couple comments. There was one technical error and he also wanted YP worked out when it was being used in the context of the code that was doing the work here. So I replaced with more generic terms or specifically called out BitBake as the responsible software. (From yocto-docs rev: 40343bf30b8492757f81bc0274d46931318f7120) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation/poky-ref-manual/ref-bitbake.xml: Updated BitBake Running a Task

2011-12-16T16:58:41+00:00

I added more information about how BitBake actually runs a task. The information has to do with how tightly BB controls the execution environment of the build tasks to prevent contamination from the build machine from leaking into the task execution environment. This tight control actually causes some unexpected behavior during builds. For example, when a user exports and BB_ENV_EXTRAWHITE an environment item such as CCACHE_DIR, the effects of the environment item never make it to the BB task execution environment. They only make it to the data store. The user actually has to take some extra steps to export that environment item into the task execution environment. The added information I put into the "Running a Task" section describes these extra steps. Fixes [YOCTO #689] Reported-by: Wolfgang Denk (From yocto-docs rev: 182aa61693c2c7de8331569c30cbb8f41dad2315) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documenation/poky-ref-manual/technical-details.xml: Shared State

2011-12-16T16:58:40+00:00

I updated the tips and tricks section to include two sub-sections. The first if the debugging stuff from Richard's email. The second section is how to invalidate a section of the sstate cache on a per-class basis. Fixes [YOCTO #1500] (From yocto-docs rev: 7493f5e7ec641e7cd79f8e3e6c045cadf7a6999c) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie