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 - Multilib wiki - page. - - - - Aside from this wiki page, several examples exist in the + Several examples exist in the meta-skeleton layer found in the Source Directory: @@ -3603,8 +3596,39 @@ Additional Implementation Details - 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: + + The typical convention used for the + class extension code as used by + Multilib assumes that all package names specified + in + PACKAGES + that contain ${PN} have + ${PN} at the start of the name. + When that convention is not followed and + ${PN} appears at + the middle or the end of a name, problems occur. + + The + TARGET_VENDOR + value under Multilib will be extended to + "-vendormlmultilib" + (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 + config.sub, and + other separators are problematic for different + reasons. + + + +' + For the RPM Package Management System, the following implementation details exist: