Build history collects similar information on the contents
of SDKs
(e.g. bitbake -c populate_sdk imagename
)
as compared to information it collects for images.
Furthermore, this information differs depending on whether
an extensible or standard SDK is being produced.
The following list shows the files produced for SDKs:
files-in-sdk.txt:
A list of files in the SDK with permissions,
owner, group, size, and symlink information.
This list includes both the host and target parts
of the SDK.
sdk-info.txt:
A text file containing name-value pairs with
information about the SDK.
See the following listing example for more
information.
sstate-task-sizes.txt:
A text file containing name-value pairs with
information about task group sizes
(e.g. do_populate_sysroot
tasks have a total size).
The sstate-task-sizes.txt
file
exists only when an extensible SDK is created.
sstate-package-sizes.txt:
A text file containing name-value pairs with
information for the shared-state packages and
sizes in the SDK.
The sstate-package-sizes.txt
file exists only when an extensible SDK is created.
sdk-files:
A folder that contains copies of the files
mentioned in
BUILDHISTORY_SDK_FILES
if the
files are present in the output.
Additionally, the default value of
BUILDHISTORY_SDK_FILES
is
specific to the extensible SDK although you can
set it differently if you would like to pull in
specific files from the standard SDK.
The default files are
conf/local.conf
,
conf/bblayers.conf
,
conf/auto.conf
,
conf/locked-sigs.inc
, and
conf/devtool.conf
.
Thus, for an extensible SDK, these files get
copied into the sdk-files
directory.
The following information appears under
each of the host
and target
directories
for the portions of the SDK that run on the host
and on the target, respectively:
depends.dot:
Dependency graph for the SDK that is
compatible with
graphviz
.
installed-package-names.txt:
A list of installed packages by name only.
installed-package-sizes.txt:
A list of installed packages ordered by size.
installed-packages.txt:
A list of installed packages with full
package filenames.
Here is an example of sdk-info.txt
:
DISTRO = poky DISTRO_VERSION = 1.3+snapshot-20130327 SDK_NAME = poky-glibc-i686-arm SDK_VERSION = 1.3+snapshot SDKMACHINE = SDKIMAGE_FEATURES = dev-pkgs dbg-pkgs BAD_RECOMMENDATIONS = SDKSIZE = 352712
Other than SDKSIZE
, which is the
total size of the files in the SDK in Kbytes, 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.