From b990aa8b1bf014fcc662da744f595f44eb8352b9 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 24 Mar 2014 16:11:10 -0600 Subject: 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 Signed-off-by: Richard Purdie --- documentation/ref-manual/introduction.xml | 183 +++++++++++++++++++++--------- 1 file changed, 131 insertions(+), 52 deletions(-) (limited to 'documentation/ref-manual/introduction.xml') diff --git a/documentation/ref-manual/introduction.xml b/documentation/ref-manual/introduction.xml index 47f736285c..7eb8203bc2 100644 --- a/documentation/ref-manual/introduction.xml +++ b/documentation/ref-manual/introduction.xml @@ -338,63 +338,142 @@ If your host development system does not meet all these requirements, - you can resolve this by either downloading a pre-built tarball - containing these tools, or building such a tarball on another - system. - Regardless of the method, once you have the tarball, you simply - 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 PATH and sets - any other environment variables required to run the tools. - Doing so gives you working versions of Git, tar, Python and - chrpath. + you can resolve this by installing a buildtools + tarball that contains these tools. + You can get the tarball one of two ways: download a pre-built + tarball or use BitBake to build the tarball. - - If downloading a pre-built tarball, locate the - *.sh at - . - +
+ Downloading a Pre-Built <filename>buildtools</filename> Tarball - - If building your own tarball, do so using this command: - - $ bitbake buildtools-tarball - - - The SDKMACHINE - variable determines whether you build tools for a 32-bit - or 64-bit system. - - Once the build completes, you can find the file that installs - the tools in the tmp/deploy/sdk subdirectory - of the - Build Directory. - The file used to install the tarball has the string "buildtools" - in the name. - + + Downloading and running a pre-built buildtools installer is + the easiest of the two methods by which you can get these tools: + + + Locate and download the *.sh at + . + + + Execute the installation script. + Here is an example: + + $ sh poky-eglibc-x86_64-buildtools-tarball-x86_64-buildtools-nativesdk-standalone-&DISTRO;.sh + + During execution, a prompt appears that allows you to + choose the installation directory. + For example, you could choose the following: + + /home/your-username/buildtools + + + + Source the tools environment setup script by using a + command like the following: + + $ source /home/your-username/buildtools/environment-setup-i586-poky-linux + + Of course, you need to supply your installation directory and be + sure to use the right file (i.e. i585 or x86-64). + + + After you have sourced the setup script, + the tools are added to PATH + and any other environment variables required to run the + tools are initialized. + The results are working versions versions of Git, tar, + Python and chrpath. + + + +
- - After you have either built the tarball or downloaded it, you need - to install it. - Install the tools by executing the *.sh file. - During execution, a prompt appears that allows you to choose the - installation directory. - For example, you could choose the following: - - /home/your-username/sdk - - +
+ Building Your Own <filename>buildtools</filename> Tarball - - The final step before you can actually use the tools is to source - the tools environment with a command like the following: - - $ source /home/your-username/sdk/environment-setup-i586-poky-linux - - Of course, you need to supply your installation directory and be - sure to use the right file (i.e. i585 or x86-64). - + + 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 + .sh file and then + take steps to transfer and run it on a + machine that does not meet the minimal Git, tar, and Python + requirements. + + + + Here are the steps to take to build and run your own + buildtools installer: + + + On the machine that is able to run BitBake, + be sure you have set up your build environment with + the setup script + (&OE_INIT_FILE; + or + oe-init-build-env-memres). + + + Run the BitBake command to build the tarball: + + $ bitbake buildtools-tarball + + + The + SDKMACHINE + variable in your local.conf file + determines whether you build tools for a 32-bit + or 64-bit system. + + Once the build completes, you can find the + .sh file that installs + the tools in the tmp/deploy/sdk + subdirectory of the + Build Directory. + The installer file has the string "buildtools" + in the name. + + + Transfer the .sh file from the + build host to the machine that does not meet the + Git, tar, or Python requirements. + + + On the machine that does not meet the requirements, + run the .sh file + to install the tools. + Here is an example: + + $ sh poky-eglibc-x86_64-buildtools-tarball-x86_64-buildtools-nativesdk-standalone-&DISTRO;.sh + + During execution, a prompt appears that allows you to + choose the installation directory. + For example, you could choose the following: + + /home/your-username/buildtools + + + + Source the tools environment setup script by using a + command like the following: + + $ source /home/your-username/buildtools/environment-setup-i586-poky-linux + + Of course, you need to supply your installation directory and be + sure to use the right file (i.e. i585 or x86-64). + + + After you have sourced the setup script, + the tools are added to PATH + and any other environment variables required to run the + tools are initialized. + The results are working versions versions of Git, tar, + Python and chrpath. + + + +
-- cgit v1.2.3-54-g00ecf