diff options
| author |   Scott Rifenbark <srifenbark@gmail.com> | 2016-10-11 07:36:00 -0700 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-10-13 23:16:46 +0100 |
| commit | 551f7d87c9fb6e4652afd6a921c9e4f816ebc2b7 (patch) | |
| tree | 9c8d1df9b2439ab26e6d93bb8bc997db8035c947 /documentation | |
| parent | cbc59866f3b92b71d8542ef975467c2dbb4b2a88 (diff) | |
| download | openembedded-core-contrib-551f7d87c9fb6e4652afd6a921c9e4f816ebc2b7.tar.gz | |
dev-manual: Applied review comments to "Packaging Externally Produced Binaries"
Fixes [YOCTO #10392]
Moved the last bullet item from the list that was about
DEPENDS to a note form above the list. This was done because
the stuff for DEPENDS is more general.
(From yocto-docs rev: 2879d97b14322f1f9495288fc7f2298a186c5f68)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
| -rw-r--r-- | documentation/dev-manual/dev-manual-common-tasks.xml | 50 |
1 files changed, 28 insertions, 22 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 33faddcca6..5c7284238d 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -3336,10 +3336,37 @@ <ulink url='&YOCTO_DOCS_REF_URL;#var-D'><filename>D</filename></ulink> variables in the Yocto Project Reference Manual's variable glossary. + <note><title>Notes</title> + <itemizedlist> + <listitem><para> + Using + <ulink url='&YOCTO_DOCS_REF_URL;#var-DEPENDS'><filename>DEPENDS</filename></ulink> + is a good idea even for components distributed + in binary form, and is often necessary for + shared libraries. + For a shared library, listing the library + dependencies in + <filename>DEPENDS</filename> makes sure that + the libraries are available in the staging + sysroot when other recipes link against the + library, which might be necessary for + successful linking. + </para></listitem> + <listitem><para> + Using <filename>DEPENDS</filename> also + allows runtime dependencies between packages + to be added automatically. + See the + "<ulink url='&YOCTO_DOCS_REF_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>" + section in the Yocto Project Reference Manual + for more information. + </para></listitem> + </itemizedlist> + </note> </para> <para> - If you can't use the <filename>bin_package</filename> + If you cannot use the <filename>bin_package</filename> class, you need to be sure you are doing the following: <itemizedlist> <listitem><para> @@ -3391,27 +3418,6 @@ and whether those files are in different locations than the defaults. </para></listitem> - <listitem><para> - Using - <ulink url='&YOCTO_DOCS_REF_URL;#var-DEPENDS'><filename>DEPENDS</filename></ulink> - is a good idea even for components distributed in - binary form, and is often necessary for shared - libraries. - For a shared library, listing the library - dependencies in - <filename>DEPENDS</filename> makes sure that the - libraries are available in the staging sysroot when - other recipes link against the library, which might - be necessary for successful linking.</para> - - <para>Using <filename>DEPENDS</filename> also - allows runtime dependencies between packages to be - added automatically. - See the - "<ulink url='&YOCTO_DOCS_REF_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>" - section in the Yocto Project Reference Manual for - more information. - </para></listitem>. </itemizedlist> </para> </section> |