diff options
Diffstat (limited to 'documentation/ref-manual/faq.xml')
| -rw-r--r-- | documentation/ref-manual/faq.xml | 30 |
1 files changed, 9 insertions, 21 deletions
diff --git a/documentation/ref-manual/faq.xml b/documentation/ref-manual/faq.xml index 69b679bbf7..af8797bbf5 100644 --- a/documentation/ref-manual/faq.xml +++ b/documentation/ref-manual/faq.xml | |||
| @@ -31,31 +31,19 @@ | |||
| 31 | <qandaentry> | 31 | <qandaentry> |
| 32 | <question> | 32 | <question> |
| 33 | <para> | 33 | <para> |
| 34 | I only have Python 2.4 or 2.5 but BitBake requires Python 2.6 or 2.7. | 34 | My development system does not have Python 2.7.3 or greater, |
| 35 | which the Yocto Project requires. | ||
| 35 | Can I still use the Yocto Project? | 36 | Can I still use the Yocto Project? |
| 36 | </para> | 37 | </para> |
| 37 | </question> | 38 | </question> |
| 38 | <answer> | 39 | <answer> |
| 39 | <para> | 40 | <para> |
| 40 | You can use a stand-alone tarball to provide Python 2.6. | 41 | You can get the required tools on your host development |
| 41 | You can find pre-built 32 and 64-bit versions of Python 2.6 at the following locations: | 42 | system a couple different ways (i.e. building a tarball or |
| 42 | <itemizedlist> | 43 | downloading a tarball). |
| 43 | <listitem><para><ulink url='&YOCTO_PYTHON-i686_DL_URL;'>32-bit tarball</ulink></para></listitem> | 44 | See the |
| 44 | <listitem><para><ulink url='&YOCTO_PYTHON-x86_64_DL_URL;'>64-bit tarball</ulink></para></listitem> | 45 | "<link linkend='required-git-tar-and-python-versions'>Required Git, tar, and Python Versions</link>" |
| 45 | </itemizedlist> | 46 | section for steps on how to update your build tools. |
| 46 | </para> | ||
| 47 | <para> | ||
| 48 | These tarballs are self-contained with all required libraries and should work | ||
| 49 | on most Linux systems. | ||
| 50 | To use the tarballs extract them into the root | ||
| 51 | directory and run the appropriate command: | ||
| 52 | <literallayout class='monospaced'> | ||
| 53 | $ export PATH=/opt/poky/sysroots/i586-pokysdk-linux/usr/bin/:$PATH | ||
| 54 | $ export PATH=/opt/poky/sysroots/x86_64-pokysdk-linux/usr/bin/:$PATH | ||
| 55 | </literallayout> | ||
| 56 | </para> | ||
| 57 | <para> | ||
| 58 | Once you run the command, BitBake uses Python 2.6. | ||
| 59 | </para> | 47 | </para> |
| 60 | </answer> | 48 | </answer> |
| 61 | </qandaentry> | 49 | </qandaentry> |
| @@ -682,7 +670,7 @@ | |||
| 682 | <para> | 670 | <para> |
| 683 | Yes - you can easily do this. | 671 | Yes - you can easily do this. |
| 684 | When you use BitBake to build an image, all the build output | 672 | When you use BitBake to build an image, all the build output |
| 685 | goes into the directory created when you run the | 673 | goes into the directory created when you run the |
| 686 | build environment setup script (i.e. | 674 | build environment setup script (i.e. |
| 687 | <link linkend='structure-core-script'><filename>&OE_INIT_FILE;</filename></link> | 675 | <link linkend='structure-core-script'><filename>&OE_INIT_FILE;</filename></link> |
| 688 | or | 676 | or |