sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

ref-manual, yocto-project-qs: Notes and infor for buildtools issues 

Fixes [YOCTO #4866]

Updated the main area where it talks about needing the right
versions of Git, tar, and Python.  You can get this set up using a
couple methods.  I documented both.

The changes in the FAQ and in the QS are basically notes that point
to that section for more information.

(From yocto-docs rev: 1b64c7c271303ecf10ec85c8a2cd5a0d909f1151)

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 2014-03-24 16:11:10 -06:00 committed by Richard Purdie
parent 752bf31c85
commit b990aa8b1b
3 changed files with 144 additions and 62 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
documentation/ref-manual/faq.xml
View File

@ -30,9 +30,12 @@
<qandaentry> <qandaentry>
<question> <question>
<para> <para id='faq-not-meeting-requirements'>
My development system does not have Python 2.7.3 or greater, My development system does not meet the
which the Yocto Project requires. required Git, tar, and Python versions.
In particular, I do not have Python 2.7.3 or greater, or
I do have Python 3.x, which is specifically not supported by
the Yocto Project.
Can I still use the Yocto Project? Can I still use the Yocto Project?
</para> </para>
</question> </question>

185
documentation/ref-manual/introduction.xml
View File

@ -338,63 +338,142 @@
<para> <para>
If your host development system does not meet all these requirements, If your host development system does not meet all these requirements,
you can resolve this by either downloading a pre-built tarball you can resolve this by installing a <filename>buildtools</filename>
containing these tools, or building such a tarball on another tarball that contains these tools.
system. You can get the tarball one of two ways: download a pre-built
Regardless of the method, once you have the tarball, you simply tarball or use BitBake to build the tarball.
install it somewhere on your system, such as a directory in your
home directory, and then source the environment script provided,
which adds the tools into <filename>PATH</filename> and sets
any other environment variables required to run the tools.
Doing so gives you working versions of Git, tar, Python and
<filename>chrpath</filename>.
</para> </para>
<para> <section id='downloading-a-pre-built-buildtools-tarball'>
If downloading a pre-built tarball, locate the <title>Downloading a Pre-Built <filename>buildtools</filename> Tarball</title>
<filename>*.sh</filename> at
<ulink url='&YOCTO_DL_URL;/releases/yocto/yocto-&DISTRO;/buildtools/'></ulink>.
</para>
<para> <para>
If building your own tarball, do so using this command: Downloading and running a pre-built buildtools installer is
<literallayout class='monospaced'> the easiest of the two methods by which you can get these tools:
<orderedlist>
<listitem><para>
Locate and download the <filename>*.sh</filename> at
<ulink url='&YOCTO_DL_URL;/releases/yocto/yocto-&DISTRO;/buildtools/'></ulink>.
</para></listitem>
<listitem><para>
Execute the installation script.
Here is an example:
<literallayout class='monospaced'>
$ sh poky-eglibc-x86_64-buildtools-tarball-x86_64-buildtools-nativesdk-standalone-&DISTRO;.sh
</literallayout>
During execution, a prompt appears that allows you to
choose the installation directory.
For example, you could choose the following:
<literallayout class='monospaced'>
/home/your-username/buildtools
</literallayout>
</para></listitem>
<listitem><para>
Source the tools environment setup script by using a
command like the following:
<literallayout class='monospaced'>
$ source /home/your-username/buildtools/environment-setup-i586-poky-linux
</literallayout>
Of course, you need to supply your installation directory and be
sure to use the right file (i.e. i585 or x86-64).
</para>
<para>
After you have sourced the setup script,
the tools are added to <filename>PATH</filename>
and any other environment variables required to run the
tools are initialized.
The results are working versions versions of Git, tar,
Python and <filename>chrpath</filename>.
</para></listitem>
</orderedlist>
</para>
</section>
<section id='building-your-own-buildtools-tarball'>
<title>Building Your Own <filename>buildtools</filename> Tarball</title>
<para>
Building and running your own buildtools installer applies
only when you have a build host that can already run BitBake.
In this case, you use that machine to build the
<filename>.sh</filename> file and then
take steps to transfer and run it on a
machine that does not meet the minimal Git, tar, and Python
requirements.
</para>
<para>
Here are the steps to take to build and run your own
buildtools installer:
<orderedlist>
<listitem><para>
On the machine that is able to run BitBake,
be sure you have set up your build environment with
the setup script
(<link linkend='structure-core-script'><filename>&OE_INIT_FILE;</filename></link>
or
<link linkend='structure-memres-core-script'><filename>oe-init-build-env-memres</filename></link>).
</para></listitem>
<listitem><para>
Run the BitBake command to build the tarball:
<literallayout class='monospaced'>
$ bitbake buildtools-tarball $ bitbake buildtools-tarball
</literallayout> </literallayout>
<note> <note>
The <link linkend='var-SDKMACHINE'><filename>SDKMACHINE</filename></link> The
variable determines whether you build tools for a 32-bit <link linkend='var-SDKMACHINE'><filename>SDKMACHINE</filename></link>
or 64-bit system. variable in your <filename>local.conf</filename> file
</note> determines whether you build tools for a 32-bit
Once the build completes, you can find the file that installs or 64-bit system.
the tools in the <filename>tmp/deploy/sdk</filename> subdirectory </note>
of the Once the build completes, you can find the
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>. <filename>.sh</filename> file that installs
The file used to install the tarball has the string "buildtools" the tools in the <filename>tmp/deploy/sdk</filename>
in the name. subdirectory of the
</para> <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
The installer file has the string "buildtools"
<para> in the name.
After you have either built the tarball or downloaded it, you need </para></listitem>
to install it. <listitem><para>
Install the tools by executing the <filename>*.sh</filename> file. Transfer the <filename>.sh</filename> file from the
During execution, a prompt appears that allows you to choose the build host to the machine that does not meet the
installation directory. Git, tar, or Python requirements.
For example, you could choose the following: </para></listitem>
<literallayout class='monospaced'> <listitem><para>
/home/your-username/sdk On the machine that does not meet the requirements,
</literallayout> run the <filename>.sh</filename> file
</para> to install the tools.
Here is an example:
<para> <literallayout class='monospaced'>
The final step before you can actually use the tools is to source $ sh poky-eglibc-x86_64-buildtools-tarball-x86_64-buildtools-nativesdk-standalone-&DISTRO;.sh
the tools environment with a command like the following: </literallayout>
<literallayout class='monospaced'> During execution, a prompt appears that allows you to
$ source /home/your-username/sdk/environment-setup-i586-poky-linux choose the installation directory.
</literallayout> For example, you could choose the following:
Of course, you need to supply your installation directory and be <literallayout class='monospaced'>
sure to use the right file (i.e. i585 or x86-64). /home/your-username/buildtools
</para> </literallayout>
</para></listitem>
<listitem><para>
Source the tools environment setup script by using a
command like the following:
<literallayout class='monospaced'>
$ source /home/your-username/buildtools/environment-setup-i586-poky-linux
</literallayout>
Of course, you need to supply your installation directory and be
sure to use the right file (i.e. i585 or x86-64).
</para>
<para>
After you have sourced the setup script,
the tools are added to <filename>PATH</filename>
and any other environment variables required to run the
tools are initialized.
The results are working versions versions of Git, tar,
Python and <filename>chrpath</filename>.
</para></listitem>
</orderedlist>
</para>
</section>
</section> </section>
</section> </section>

12
documentation/yocto-project-qs/yocto-project-qs.xml
View File

@ -533,12 +533,12 @@
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ bitbake -k core-image-sato $ bitbake -k core-image-sato
</literallayout> </literallayout>
<note><para> <note>
BitBake requires Python 2.6 or 2.7. For more information on this requirement, BitBake requires Python 2.6 or 2.7. For more information on
see the this requirement, see the
<ulink url='&YOCTO_DOCS_REF_URL;#faq'>FAQ</ulink> in the Yocto Project Reference "<ulink url='&YOCTO_DOCS_REF_URL;#required-git-tar-and-python-versions'>Required Git, tar, and Python</ulink>"
Manual. section in the Yocto Project Reference Manual.
</para></note> </note>
The final command runs the image: The final command runs the image:
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ runqemu qemux86 $ runqemu qemux86