sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

ref-manual: Edits to buildhistory patch 1 of 5. 

I did a bit of cleanup on the text from Paul's patch number 1.
Just some active voice stuff mainly.

(From yocto-docs rev: f08fa3da997e53c587e3f17ef908e41594654db3)

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 2013-04-04 07:25:09 -07:00 committed by Richard Purdie
parent 58122bf063
commit 67f4fd4ffa
1 changed files with 24 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

44
documentation/ref-manual/usingpoky.xml
View File

@ -635,15 +635,15 @@
<title>Build History SDK Information</title>
<para>
Build history collects similar information on the contents
of SDKs (for example, <filename>meta-toolchain</filename>
of SDKs (e.g., <filename>meta-toolchain</filename>
or <filename>bitbake -c populate_sdk imagename</filename>)
to that which it collects for images.
The files produced for each SDK are as follows:
as compared to information it collects for images.
The following list shows the files produced for each SDK:
<itemizedlist>
<listitem><para><filename>files-in-sdk.txt:</filename>
A list of files in the SDK with permissions,
owner, group, size, and symlink information.
This includes both the host and target parts
This list includes both the host and target parts
of the SDK.
</para></listitem>
<listitem><para><filename>sdk-info.txt:</filename>
@ -651,16 +651,19 @@
about the SDK.
See the following listing example for more information.
</para></listitem>
<listitem><para>Under each of the <filename>host</filename> and
<filename>target</filename> directories (for the portions of the
SDK that run on the host and on the target respectively):
<listitem><para>The following information appears under
each of the <filename>host</filename>
and <filename>target</filename> directories
for the portions of the SDK that run on the host and
on the target, respectively:
<itemizedlist>
<listitem><para><filename>depends.dot:</filename>
Dependency graph for the SDK that is
Dependency graph for the SDK that is
compatible with <filename>graphviz</filename>.
</para></listitem>
<listitem><para><filename>installed-package-names.txt:</filename>
A list of installed packages by name only.</para></listitem>
A list of installed packages by name only.
</para></listitem>
<listitem><para><filename>installed-package-sizes.txt:</filename>
A list of installed packages ordered by size.
</para></listitem>
@ -675,21 +678,22 @@
<para>
Here is an example of <filename>sdk-info.txt</filename>:
<literallayout class='monospaced'>
DISTRO = poky
DISTRO_VERSION = 1.3+snapshot-20130327
SDK_NAME = poky-eglibc-i686-arm
SDK_VERSION = 1.3+snapshot
SDKMACHINE =
SDKIMAGE_FEATURES = dev-pkgs dbg-pkgs
BAD_RECOMMENDATIONS =
SDKSIZE = 352712
DISTRO = poky
DISTRO_VERSION = 1.3+snapshot-20130327
SDK_NAME = poky-eglibc-i686-arm
SDK_VERSION = 1.3+snapshot
SDKMACHINE =
SDKIMAGE_FEATURES = dev-pkgs dbg-pkgs
BAD_RECOMMENDATIONS =
SDKSIZE = 352712
</literallayout>
Other than <filename>SDKSIZE</filename>, which is the
total size of the files in the SDK in Kbytes, the
name-value pairs are variables that may have influenced the
name-value pairs are variables that might have influenced the
content of the SDK.
This information is often useful when you are trying to determine
why a change in the package or file listings has occurred.
This information is often useful when you are trying to
determine why a change in the package or file listings
has occurred.
</para>
</section>