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

ref-manual: Updated the FAQ entry about old Python version 

I re-wrote this FAQ entry to indicate more recent versions of
Python and to leverage off the way we can now download or build
out the buildtools.

Reported-by: Paul Eggleton <paul.eggleton@linux.intel.com>
(From yocto-docs rev: 87bcd154526feac7218a27b62bffd3a017885435)

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-11-08 07:28:08 -08:00 committed by Richard Purdie
parent 9addcf5ccb
commit f63ae44a8e
1 changed files with 9 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -31,31 +31,19 @@
<qandaentry> <qandaentry>
<question> <question>
<para> <para>
I only have Python 2.4 or 2.5 but BitBake requires Python 2.6 or 2.7. My development system does not have Python 2.7.3 or greater,
which the Yocto Project requires.
Can I still use the Yocto Project? Can I still use the Yocto Project?
</para> </para>
</question> </question>
<answer> <answer>
<para> <para>
You can use a stand-alone tarball to provide Python 2.6. You can get the required tools on your host development
You can find pre-built 32 and 64-bit versions of Python 2.6 at the following locations: system a couple different ways (i.e. building a tarball or
<itemizedlist> downloading a tarball).
<listitem><para><ulink url='&YOCTO_PYTHON-i686_DL_URL;'>32-bit tarball</ulink></para></listitem> See the
<listitem><para><ulink url='&YOCTO_PYTHON-x86_64_DL_URL;'>64-bit tarball</ulink></para></listitem> "<link linkend='required-git-tar-and-python-versions'>Required Git, tar, and Python Versions</link>"
</itemizedlist> section for steps on how to update your build tools.
</para>
<para>
These tarballs are self-contained with all required libraries and should work
on most Linux systems.
To use the tarballs extract them into the root
directory and run the appropriate command:
<literallayout class='monospaced'>
$ export PATH=/opt/poky/sysroots/i586-pokysdk-linux/usr/bin/:$PATH
$ export PATH=/opt/poky/sysroots/x86_64-pokysdk-linux/usr/bin/:$PATH
</literallayout>
</para>
<para>
Once you run the command, BitBake uses Python 2.6.
</para> </para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -682,7 +670,7 @@
<para> <para>
Yes - you can easily do this. Yes - you can easily do this.
When you use BitBake to build an image, all the build output When you use BitBake to build an image, all the build output
goes into the directory created when you run the goes into the directory created when you run the
build environment setup script (i.e. build environment setup script (i.e.
<link linkend='structure-core-script'><filename>&OE_INIT_FILE;</filename></link> <link linkend='structure-core-script'><filename>&OE_INIT_FILE;</filename></link>
or or