Yocto Toolchain installation: Difference between revisions

Latest revision as of 10:33, 19 April 2024

Warning: This page is designed to be used with a 'release' URL parameter.

This page is using the default release RELEASE_MORTY_V1.0_DART-6UL.
To view this page for a specific Variscite SoM and software release, please follow these steps:

Visit variwiki.com
Select your SoM
Select the software release

Yocto toolchain installation for out of Yocto builds

Prerequisites

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

Setup the environment:

$ cd ~/var-fslc-yocto
$ MACHINE=imx6ul-var-dart DISTRO=fslc-x11 . setup-environment build_x11

Build the toolchain:

$  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

The SDK should match the rootfs image on the target, otherwise you may experience difficulties when trying to debug application failures.

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

@@ Line 1: / Line 1: @@
 <!-- Set release according to "release" parameter in URL and use RELEASE_MORTY_V1.0_DART-6UL as default
---> {{#vardefine:RELEASE_PARAM|{{#urlget:release|RELEASE_MORTY_V1.0_DART-6UL}}}} <!--
+--> {{INIT_RELEASE_PARAM|RELEASE_MORTY_V1.0_DART-6UL}}<!--
 --> {{#lst:Yocto_Platform_Customization|{{#var:RELEASE_PARAM}}}} <!--
+--> {{#lst:Debian_Platform_Customization|{{#var:RELEASE_PARAM}}}} <!--
 --> {{#lst:B2QT_Platform_Customization|{{#var:RELEASE_PARAM}}}} <!--
---> {{#varexists:DEFAULT_IMAGE_BB_NAME | | {{ #vardefine:DEFAULT_IMAGE_BB_NAME | fsl-image-gui }} }} <!--
+-->{{#switch:{{#var:SOC_FAMILY}}
--->{{#vardefine:TOOLCHAIN_INSTALL_NAME | {{ #varexists:TOOLCHAIN_INSTALL_B2QT_NAME | {{#var:TOOLCHAIN_INSTALL_B2QT_NAME}} | {{#ifeq: {{#var:SOC_SERIES}}|imx8|{{#var:TOOLCHAIN_INSTALL_XWAYLAND_NAME}}|{{#var:TOOLCHAIN_INSTALL_X11_NAME}}}} }} }}<!--
+|am6={{Yocto_Toolchain_installation_AM62}}
---> {{PageHeader|Yocto toolchain installation for out of Yocto builds}} {{DocImage|category1=Yocto|category2={{#var:HARDWARE_NAME}}}} __toc__
+|am3={{Yocto_Toolchain_installation_AM62}}
+|#default={{Yocto_Toolchain_installation_IMX}}
-== Prerequirements ==
+}}
-A full Yocto build environment is required for the toolchain generation.<br>
-To setup a Yocto build environment follow steps 1 & 3 of the {{Varlink|Yocto_Build_Release|{{#var:RELEASE_LINK}}|Build Yocto from source code}} guide and then proceed to either the toolchain or complete SDK steps below:
-== Build a toolchain ==
-{{#lst:Yocto_Platform_Customization|YOCTO_ENV_SETUP_X}}
- $ bitbake meta-ide-support
- $ bitbake meta-toolchain{{#ifeq: {{#var:BUILD_FOLDER}}|~/var-b2qt|-b2qt-embedded-qt5-sdk|}}
-== 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.
-{{#lst:Yocto_Platform_Customization|YOCTO_ENV_SETUP_X}}
-E.g. when using the {{#var:DEFAULT_IMAGE_BB_NAME}} image:
- $ bitbake -c populate_sdk {{#var:DEFAULT_IMAGE_BB_NAME}}
-{{Note|The SDK should match the rootfs image on the target, otherwise you may experience difficulties when trying to debug application failures.}}
-== Install the toolchain/SDK ==
-Install the tools by running the resulted script in tmp/deploy/sdk/.
-E.g.
- $ tmp/deploy/sdk/{{#var:TOOLCHAIN_INSTALL_NAME}}
-Note: The toolchain/script name depends on your build machine and the bitbaked image/recipe, and may change.<br>
-<br>
-Accept all the default options, and at the end of the installation you should see the following:
-<pre>
-SDK has been successfully set up and is ready to be used.
-</pre>
-== 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 {{#var:TOOLCHAIN_LOCATION}}{{#ifeq: {{#var:SOC_SERIES}}|imx8|<br>$ export LDFLAGS=|}}