Yocto Toolchain installation: Difference between revisions
No edit summary |
|||
Line 10: | Line 10: | ||
== Build a toolchain == | == Build a toolchain == | ||
$ cd {{#var:BUILD_FOLDER}} | $ cd {{#var:BUILD_FOLDER}} | ||
$ MACHINE={{#var:MACHINE_NAME}} DISTRO={{#var:BUILD_DISTRO}} {{#var:BUILD_SCRIPT}} {{#ifeq: {{#var: | $ MACHINE={{#var:MACHINE_NAME}} DISTRO={{#var:BUILD_DISTRO}} {{#var:BUILD_SCRIPT}} {{#ifeq: {{#var:SOC_SERIES}}|imx8|-b {{#var:BUILD_FOLDER_XWAYLAND}}|{{#var:BUILD_FOLDER_X11}}}} | ||
$ bitbake meta-ide-support | $ bitbake meta-ide-support | ||
Line 19: | Line 19: | ||
To compile applications that require libraries other than glibc you should build an SDK which contains development versions of all libraries in the rootfs image, and not just the basic toolchain. | To compile applications that require libraries other than glibc you should build an SDK which contains development versions of all libraries in the rootfs image, and not just the basic toolchain. | ||
$ cd {{#var:BUILD_FOLDER}} | $ cd {{#var:BUILD_FOLDER}} | ||
$ MACHINE={{#var:MACHINE_NAME}} DISTRO={{#var:BUILD_DISTRO}} {{#var:BUILD_SCRIPT}} {{#ifeq: {{#var: | $ MACHINE={{#var:MACHINE_NAME}} DISTRO={{#var:BUILD_DISTRO}} {{#var:BUILD_SCRIPT}} {{#ifeq: {{#var:SOC_SERIES}}|imx8|-b {{#var:BUILD_FOLDER_XWAYLAND}}|{{#var:BUILD_FOLDER_X11}}}} | ||
E.g. when using the fsl-image-gui image: | E.g. when using the fsl-image-gui image: | ||
$ bitbake -c populate_sdk fsl-image-gui | $ bitbake -c populate_sdk fsl-image-gui | ||
Line 28: | Line 28: | ||
E.g. | E.g. | ||
$ tmp/deploy/sdk/{{#ifeq: {{#var: | $ tmp/deploy/sdk/{{#ifeq: {{#var:SOC_SERIES}}|imx8|{{#var:TOOLCHAIN_INSTALL_XWAYLAND_NAME}}|{{#var:TOOLCHAIN_INSTALL_X11_NAME}}}} | ||
Note: The toolchain/script name depends on your build machine, and the bitbaked image/recipe, and may change.<br> | Note: The toolchain/script name depends on your build machine, and the bitbaked image/recipe, and may change.<br> | ||
<br> | <br> | ||
Line 38: | Line 38: | ||
== Use the toolchain/SDK == | == Use the toolchain/SDK == | ||
Each time you wish to use the toolchain in a new shell session, you need to source the environment setup script: | Each time you wish to use the toolchain in a new shell session, you need to source the environment setup script: | ||
$ source {{#var:TOOLCHAIN_LOCATION}}{{#ifeq: {{#var: | $ source {{#var:TOOLCHAIN_LOCATION}}{{#ifeq: {{#var:SOC_SERIES}}|imx8|<br>$ export LDFLAGS=|}} |
Revision as of 14:44, 26 February 2019
Prerequirements
A full Yocto build environment is required for the toolchain generation.
To setup a Yocto build environment follow steps 1 & 3 of the Build Yocto from source code guide and then proceed to either the toolchain or complete SDK steps below:
Build a toolchain
$ cd ~/var-fslc-yocto $ MACHINE=imx6ul-var-dart DISTRO=fslc-x11 . setup-environment build_x11
$ bitbake meta-ide-support $ bitbake meta-toolchain
Build a complete SDK
To compile applications that require libraries other than glibc you should build an SDK which contains development versions of all libraries in the rootfs image, and not just the basic toolchain.
$ cd ~/var-fslc-yocto $ MACHINE=imx6ul-var-dart DISTRO=fslc-x11 . setup-environment build_x11
E.g. when using the fsl-image-gui image:
$ bitbake -c populate_sdk fsl-image-gui
Install the toolchain/SDK
Install the tools by running the resulted script in tmp/deploy/sdk/.
E.g.
$ tmp/deploy/sdk/fslc-x11-glibc-x86_64-meta-toolchain-armv7at2hf-neon-toolchain-2.2.1.sh
Note: The toolchain/script name depends on your build machine, and the bitbaked image/recipe, and may change.
Accept all the default options, and at the end of the installation you should see the following:
SDK has been successfully set up and is ready to be used.
Use the toolchain/SDK
Each time you wish to use the toolchain in a new shell session, you need to source the environment setup script:
$ source /opt/fslc-x11/2.2.1/environment-setup-armv7at2hf-neon-fslc-linux-gnueabi