ref-manual: Edits the x32 section.

these edits are on the fly with Saul Wold.  Probably more to
come.  They are eliminating some of the "new" wording and
other bullets that are out of date.

(From yocto-docs rev: 9e5da05f722e1e17af91e1831e34a69a3df79dcc)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2013-04-02 16:23:24 -07:00 committed by Richard Purdie
parent 95c36b7cc2
commit 9e5fd1c01d
1 changed files with 5 additions and 31 deletions

View File

@ -632,10 +632,6 @@
<itemizedlist> <itemizedlist>
<listitem><para>You can create packages and images in x32 psABI format on x86_64 architecture targets. <listitem><para>You can create packages and images in x32 psABI format on x86_64 architecture targets.
</para></listitem> </para></listitem>
<listitem><para>You can use the x32 psABI support through the <filename>meta-x32</filename>
layer on top of the OE-core/Yocto layer.</para></listitem>
<listitem><para>The toolchain from the <filename>experimental/meta-x32</filename> layer
is used for building x32 psABI program binaries.</para></listitem>
<listitem><para>You can successfully build many recipes with the x32 toolchain.</para></listitem> <listitem><para>You can successfully build many recipes with the x32 toolchain.</para></listitem>
<listitem><para>You can create and boot <filename>core-image-minimal</filename> and <listitem><para>You can create and boot <filename>core-image-minimal</filename> and
<filename>core-image-sato</filename> images.</para></listitem> <filename>core-image-sato</filename> images.</para></listitem>
@ -643,12 +639,12 @@
</para> </para>
</section> </section>
<section id='future-development-and-limitations'> <section id='stabilizing-and-completing-x32'>
<title>Future Development and Limitations</title> <title>Stabilizing and Completing x32</title>
<para> <para>
As of this Yocto Project release, the x32 psABI kernel and library interfaces As of this Yocto Project release, the x32 psABI kernel and library
specifications are not finalized. interfaces specifications are not finalized.
</para> </para>
<para> <para>
@ -658,8 +654,6 @@
work with and support x32 toolchains.</para></listitem> work with and support x32 toolchains.</para></listitem>
<listitem><para>Enhance RPM Package Manager (RPM) support for x32 binaries.</para></listitem> <listitem><para>Enhance RPM Package Manager (RPM) support for x32 binaries.</para></listitem>
<listitem><para>Support larger images.</para></listitem> <listitem><para>Support larger images.</para></listitem>
<listitem><para>Integrate x32 recipes, toolchain, and kernel changes from
<filename>experimental/meta-x32</filename> into OE-core.</para></listitem>
</itemizedlist> </itemizedlist>
</para> </para>
</section> </section>
@ -668,28 +662,8 @@
<title>Using x32 Right Now</title> <title>Using x32 Right Now</title>
<para> <para>
Despite the fact the x32 psABI support is in development state for this release of the Follow these steps to use the x32 spABI:
Yocto Project, you can follow these steps to use the x32 spABI:
<itemizedlist> <itemizedlist>
<listitem><para>Add the <filename>experimental/meta-x32</filename> layer to your local
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
You can find the <filename>experimental/meta-x32</filename> source repository at
<ulink url='&YOCTO_GIT_URL;'></ulink>.</para></listitem>
<listitem><para>Edit your <filename>conf/bblayers.conf</filename> file so that it includes
the <filename>meta-x32</filename>.
Here is an example:
<literallayout class='monospaced'>
BBLAYERS ?= " \
/home/nitin/prj/poky.git/meta \
/home/nitin/prj/poky.git/meta-yocto \
/home/nitin/prj/poky.git/meta-yocto-bsp \
/home/nitin/prj/meta-x32.git \
"
BBLAYERS_NON_REMOVABLE ?= " \
/home/nitin/prj/poky.git/meta \
/home/nitin/prj/poky.git/meta-yocto \
"
</literallayout></para></listitem>
<listitem><para>Enable the x32 psABI tuning file for <filename>x86_64</filename> <listitem><para>Enable the x32 psABI tuning file for <filename>x86_64</filename>
machines by editing the <filename>conf/local.conf</filename> like this: machines by editing the <filename>conf/local.conf</filename> like this:
<literallayout class='monospaced'> <literallayout class='monospaced'>