summaryrefslogtreecommitdiffstats
path: root/documentation/adt-manual
diff options
context:
space:
mode:
authorMaxin B. John <maxin.john@enea.com>2013-10-31 08:01:25 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-11-01 17:09:59 +0000
commit98f631a76b011832d283dc3590b4a7c32c69903b (patch)
tree10c5feedd9475660d4e278eb9b33c5c380f56900 /documentation/adt-manual
parent3abf3a6e76f77985d6499771426c357502d016cf (diff)
downloadast2050-yocto-poky-98f631a76b011832d283dc3590b4a7c32c69903b.zip
ast2050-yocto-poky-98f631a76b011832d283dc3590b4a7c32c69903b.tar.gz
adt-manual: Added note for static builds using -c populate_sdk
Documentation fix for [YOCTO #5347] SDK created useing the "-c populate_sdk" will not support static binary build without proper staticdev library packages. I have added a note to inform the user about this limitation. (From yocto-docs rev: 91409d77d68e55f4089cab3e7f48dd385dddff2e) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/adt-manual')
-rw-r--r--documentation/adt-manual/adt-prepare.xml25
1 files changed, 20 insertions, 5 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 152c7fb..02416b3 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -617,12 +617,27 @@
variable is correctly set if you are building a toolchain designed to
run on an architecture that differs from your current development host
machine (i.e. the build machine).
- </para>
+ </para>
- <para>
- When the BitBake command completes, the toolchain installer will be in
- <filename>tmp/deploy/sdk</filename> in the Build Directory.
- </para>
+ <para>
+ When the BitBake command completes, the toolchain installer will be in
+ <filename>tmp/deploy/sdk</filename> in the Build Directory.
+ <note>
+ By default, this toolchain does not build static binaries.
+ If you want to use the toolchain to build these types of libraries,
+ you need to be sure your image has the appropriate static
+ development libraries.
+ Use the
+ <ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_INSTALL'><filename>IMAGE_INSTALL</filename></ulink>
+ variable inside your <filename>local.conf</filename> file to
+ install the appropriate library packages.
+ Following is an example using <filename>eglibc</filename> static
+ development libraries:
+ <literallayout class='monospaced'>
+ IMAGE_INSTALL_append = " eglibc-staticdev"
+ </literallayout>
+ </note>
+ </para>
</section>
</chapter>
OpenPOWER on IntegriCloud