path: root/documentation/dev-manual/dev-manual-common-tasks.xml
diff options
authorScott Rifenbark <srifenbark@gmail.com>2016-04-12 12:39:39 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-04-18 16:28:23 +0100
commitecb2eb66769e651941a10e6a55a3b0654da752a3 (patch)
tree7ae052205ed3fe61e1003d037c0d35dbbdc18191 /documentation/dev-manual/dev-manual-common-tasks.xml
parent004b939d1b5882db65d882633d3a3b8d22814779 (diff)
dev-manual: Updated "Additional Implementation Details" section
Fixes [YOCTO #5517] I added two package management system generic implementation details to the section. This brings the section up to speed as the definitive work on combining multiple versions of library files into one image. We no longer have to refer the reader to a separate wiki page. (From yocto-docs rev: 450e718ca1b853f332c4e607a5a76efd689f7769) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual/dev-manual-common-tasks.xml')
1 files changed, 34 insertions, 10 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 828fbf4c3a..00cad99599 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -3495,14 +3495,7 @@
- This section overviews the Multilib process only.
- For more details on how to implement Multilib, see the
- <ulink url='&YOCTO_WIKI_URL;/wiki/Multilib'>Multilib</ulink> wiki
- page.
- </para>
- <para>
- Aside from this wiki page, several examples exist in the
+ Several examples exist in the
<filename>meta-skeleton</filename> layer found in the
<link linkend='source-directory'>Source Directory</link>:
@@ -3603,8 +3596,39 @@
<title>Additional Implementation Details</title>
- Different packaging systems have different levels of native Multilib
- support.
+ Generic implementation details as well as details that are
+ specific to package management systems exist.
+ Following are implementation details that exist regardless
+ of the package management system:
+ <itemizedlist>
+ <listitem><para>The typical convention used for the
+ class extension code as used by
+ Multilib assumes that all package names specified
+ in
+ <ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGES'><filename>PACKAGES</filename></ulink>
+ that contain <filename>${PN}</filename> have
+ <filename>${PN}</filename> at the start of the name.
+ When that convention is not followed and
+ <filename>${PN}</filename> appears at
+ the middle or the end of a name, problems occur.
+ </para></listitem>
+ <listitem><para>The
+ <ulink url='&YOCTO_DOCS_REF_URL;#var-TARGET_VENDOR'><filename>TARGET_VENDOR</filename></ulink>
+ value under Multilib will be extended to
+ "-<replaceable>vendor</replaceable>ml<replaceable>multilib</replaceable>"
+ (e.g. "-pokymllib32" for a "lib32" Multilib with
+ Poky).
+ The reason for this slightly unwieldy contraction
+ is that any "-" characters in the vendor
+ string presently break Autoconf's
+ <filename>config.sub</filename>, and
+ other separators are problematic for different
+ reasons.
+ </para></listitem>
+ </itemizedlist>
+ </para>
+ <para>
For the RPM Package Management System, the following implementation details