Skip to contentSkip to conversation

documentation: updates to static library support in SDK

PATCH Superseded Maxin B. John 2 participants 4 messages Jun 14, 2017 – Jun 15, 2017 1 message not in the archive

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 documentation: updates to static library support in SDK

For development purposes, static libraries need to be present only in the SDK. We do not need those static libraries in the image for most scenarios. So, replace IMAGE_INSTALL with TOOLCHAIN_TARGET_TASK in the documentation.

---
 documentation/adt-manual/adt-prepare.xml         | 8 ++++----
 documentation/sdk-manual/sdk-appendix-obtain.xml | 8 ++++----
 2 files changed, 8 insertions(+), 8 deletions(-)
documentation/adt-manual/adt-prepare.xml +4 -4
index 65df1d0..7587305 100644
@@ -684,16 +684,16 @@
         <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
+            you need to be sure your SDK has the appropriate static
             development libraries.
             Use the
-            <ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_INSTALL'><filename>IMAGE_INSTALL</filename></ulink>
+            <ulink url='&YOCTO_DOCS_REF_URL;#var-TOOLCHAIN_TARGET_TASK'><filename>TOOLCHAIN_TARGET_TASK</filename></ulink>
             variable inside your <filename>local.conf</filename> file to
-            install the appropriate library packages.
+            include the appropriate library packages in SDK.
             Following is an example using <filename>glibc</filename> static
             development libraries:
             <literallayout class='monospaced'>
-     IMAGE_INSTALL_append = " glibc-staticdev"
+     TOOLCHAIN_TARGET_TASK_append = " glibc-staticdev"
             </literallayout>
         </note>
     </para>
documentation/sdk-manual/sdk-appendix-obtain.xml +4 -4
index 3156f77..86e0eff 100644
@@ -96,16 +96,16 @@
                 <listitem><para>
                     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
+                    libraries, you need to be sure your SDK has the
                     appropriate static development libraries.
                     Use the
-                    <ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_INSTALL'><filename>IMAGE_INSTALL</filename></ulink>
+                    <ulink url='&YOCTO_DOCS_REF_URL;#var-TOOLCHAIN_TARGET_TASK'><filename>TOOLCHAIN_TARGET_TASK</filename></ulink>
                     variable inside your <filename>local.conf</filename> file
-                    to install the appropriate library packages.
+                    to install the appropriate library packages in SDK.
                     Following is an example using <filename>glibc</filename>
                     static development libraries:
                     <literallayout class='monospaced'>
-     IMAGE_INSTALL_append = " glibc-staticdev"
+     TOOLCHAIN_TARGET_TASK_append = " glibc-staticdev"
                     </literallayout>
                     </para></listitem>
                 <listitem><para>
Signature · 1 line
2.4.0
#1 lore raw
Quoted 24 lines · Maxin B. John

For development purposes, static libraries need to be present only in the SDK. We do not need those static libraries in the image for most scenarios. So, replace IMAGE_INSTALL with TOOLCHAIN_TARGET_TASK in the documentation.

---
 documentation/adt-manual/adt-prepare.xml         | 8 ++++----
 documentation/sdk-manual/sdk-appendix-obtain.xml | 8 ++++----
 2 files changed, 8 insertions(+), 8 deletions(-)
documentation/adt-manual/adt-prepare.xml +1 -1
index 65df1d0..7587305 100644
@@ -684,16 +684,16 @@
         <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
+            you need to be sure your SDK has the appropriate static
             development libraries.
             Use the

documentation/adt-manual/adt-prepare.xml line 696

Quoted 10 lines
documentation/adt-manual/adt-prepare.xml +3 -3
-            <ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_INSTALL'><filename>IMAGE_INSTALL</filename></ulink>
+            <ulink url='&YOCTO_DOCS_REF_URL;#var-TOOLCHAIN_TARGET_TASK'><filename>TOOLCHAIN_TARGET_TASK</filename></ulink>
             variable inside your <filename>local.conf</filename> file to
-            install the appropriate library packages.
+            include the appropriate library packages in SDK.
             Following is an example using <filename>glibc</filename> static
             development libraries:
             <literallayout class='monospaced'>
-     IMAGE_INSTALL_append = " glibc-staticdev"
+     TOOLCHAIN_TARGET_TASK_append = " glibc-staticdev"

That should perhaps be "libc-staticdev" so the same instructions work for musl (although it looks like currently musl doesn't rprovide libc-staticdev so that would need to be fixed too).

Quoted 36 lines
documentation/adt-manual/adt-prepare.xml +0 -0
             </literallayout>
         </note>
     </para>
documentation/sdk-manual/sdk-appendix-obtain.xml +4 -5
index 3156f77..86e0eff 100644
@@ -96,16 +96,16 @@
                 <listitem><para>
                     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
+                    libraries, you need to be sure your SDK has the
                     appropriate static development libraries.
                     Use the
-                    <ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_INSTALL'><filename>IMAGE_INSTALL</filename></ulink>
+                    <ulink url='&YOCTO_DOCS_REF_URL;#var-TOOLCHAIN_TARGET_TASK'><filename>TOOLCHAIN_TARGET_TASK</filename></ulink>
                     variable inside your <filename>local.conf</filename> file
-                    to install the appropriate library packages.
+                    to install the appropriate library packages in SDK.
                     Following is an example using <filename>glibc</filename>
                     static development libraries:
                     <literallayout class='monospaced'>
-     IMAGE_INSTALL_append = " glibc-staticdev"
+     TOOLCHAIN_TARGET_TASK_append = " glibc-staticdev"
                     </literallayout>
                     </para></listitem>
                 <listitem><para>
--

2.4.0

--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#2 lore raw

Hi Andre,

Quoted 31 lines · Andre McCurdy
Quoted 30 lines · Maxin B. John

For development purposes, static libraries need to be present only in the SDK. We do not need those static libraries in the image for most scenarios. So, replace IMAGE_INSTALL with TOOLCHAIN_TARGET_TASK in the documentation.

---
 documentation/adt-manual/adt-prepare.xml         | 8 ++++----
 documentation/sdk-manual/sdk-appendix-obtain.xml | 8 ++++----
 2 files changed, 8 insertions(+), 8 deletions(-)
documentation/adt-manual/adt-prepare.xml +3 -3
index 65df1d0..7587305 100644
@@ -684,16 +684,16 @@
         <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
+            you need to be sure your SDK has the appropriate static
             development libraries.
             Use the
-            <ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_INSTALL'><filename>IMAGE_INSTALL</filename></ulink>
+            <ulink url='&YOCTO_DOCS_REF_URL;#var-TOOLCHAIN_TARGET_TASK'><filename>TOOLCHAIN_TARGET_TASK</filename></ulink>
             variable inside your <filename>local.conf</filename> file to
-            install the appropriate library packages.
+            include the appropriate library packages in SDK.
             Following is an example using <filename>glibc</filename> static
Quoted 8 lines

documentation/adt-manual/adt-prepare.xml line 696

Quoted 4 lines
documentation/adt-manual/adt-prepare.xml +1 -1
             development libraries:
             <literallayout class='monospaced'>
-     IMAGE_INSTALL_append = " glibc-staticdev"
+     TOOLCHAIN_TARGET_TASK_append = " glibc-staticdev"

That should perhaps be "libc-staticdev" so the same instructions work for musl (although it looks like currently musl doesn't rprovide libc-staticdev so that would need to be fixed too).

I agree with your suggestion that examples in documentation shouldn't be specific for a particular libc implementation.

Filed a bug for musl libc-staticdev support:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=11669

Quoted 19 lines
Quoted 19 lines
documentation/adt-manual/adt-prepare.xml +0 -0
             </literallayout>
         </note>
     </para>
documentation/sdk-manual/sdk-appendix-obtain.xml +2 -3
index 3156f77..86e0eff 100644
@@ -96,16 +96,16 @@
                 <listitem><para>
                     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
+                    libraries, you need to be sure your SDK has the
                     appropriate static development libraries.
                     Use the
-                    <ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_INSTALL'><filename>IMAGE_INSTALL</filename></ulink>
+                    <ulink url='&YOCTO_DOCS_REF_URL;#var-TOOLCHAIN_TARGET_TASK'><filename>TOOLCHAIN_TARGET_TASK</filename></ulink>
                     variable inside your <filename>local.conf</filename> file
-                    to install the appropriate library packages.
Quoted 8 lines

documentation/sdk-manual/sdk-appendix-obtain.xml line 110

Quoted 8 lines
documentation/sdk-manual/sdk-appendix-obtain.xml +2 -1
+                    to install the appropriate library packages in SDK.
                     Following is an example using <filename>glibc</filename>
                     static development libraries:
                     <literallayout class='monospaced'>
-     IMAGE_INSTALL_append = " glibc-staticdev"
+     TOOLCHAIN_TARGET_TASK_append = " glibc-staticdev"
                     </literallayout>
                     </para></listitem>

Best Regards,
Maxin

A message that is not in the archive (sent off-list or not yet received): CAFNP8OtKLxr+sn2y1-scG9rf_qpJ_3=V8pirFVX7FO8xWNPSdQ@mail.gmail.com

#4 lore raw

Hi Scott,

Quoted 4 lines · Scott Rifenbark

Maxin,

Can you send out a new patch with the correction?

Sure, will send an updated patch soon.

Quoted 6 lines

Scott

Quoted 5 lines · Andre McCurdy
Quoted 3 lines · Maxin B. John

For development purposes, static libraries need to be

<snip>

Best Regards,
Maxin