View source for Template:Yocto Toolchain installation AM62

<includeonly>{{#varexists:DEFAULT_IMAGE_BB_NAME | | {{ #vardefine:DEFAULT_IMAGE_BB_NAME | var-default-image }} }} <!--
--> {{#vardefine:BB_ENV | {{#var:BB_ENV|{{#varexists: B2QT_GIT | MACHINE={{#var:MACHINE_NAME}} | }} }} }} <!--
--> {{#vardefine:B2QT_OR_YOCTO | {{#varexists: B2QT_GIT | B2QT | Yocto }} }} <!--
--> {{PageHeader|Yocto toolchain installation for out of Yocto builds}} {{DocImage|category1=Yocto|category2={{#var:HARDWARE_NAME}}}} __toc__

== Prerequisites==
A full {{#var:B2QT_OR_YOCTO}} build environment is required for the toolchain generation.<br>
To setup a {{#var:B2QT_OR_YOCTO}} build environment follow steps 1 & 3 of the {{Varlink|{{#var:B2QT_OR_YOCTO}}_Build_Release|{{#var:RELEASE_LINK}}|Build {{#var:B2QT_OR_YOCTO}} from source code}} guide and then proceed to either the toolchain or complete SDK steps below:

== Build a toolchain ==
{{#ifeq: {{#expr: {{#var:TI_RELEASE_SHORT}} < 9 }} | 1 |
TI SDK v8.x has a dedicated target for generating a toolchain. | 
}}
 $ {{#var:BB_ENV}} bitbake {{#varexists: DEFAULT_TOOLCHAIN_BB_NAME | {{#var:DEFAULT_TOOLCHAIN_BB_NAME}} | {{#varexists: B2QT_BSP_VERSION | meta-toolchain-b2qt-embedded-qt5-sdk | 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.

E.g. when using the {{#var:DEFAULT_IMAGE_BB_NAME}} image:
 $ {{#var:BB_ENV}} 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.}}
{{#ifeq: {{#expr: {{#var:TI_RELEASE_SHORT}} < 9 }} | 1 |
{{Note|TI's Yocto Dunfell Arago distribution does not officially support building the complete SDK using populate_sdk by default.<br>To fix it, dedicated patches have been introduced in Variscite BSP and are available only in the latest source code. For more information, please see [https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1202155/faq-am6x-am335x-am437x-using-a-yocto-internal-toolchain-for-target-image-builds-and-cross-development-sdk-installer-generation-with-yocto-dunfell-based-v8-x-sdks-for-sitara-mpus FAQ: AM6x/AM335x/AM437x: Using a Yocto-internal toolchain for target image builds and cross-development SDK installer generation with Yocto Dunfell-based v8.x SDKs for Sitara MPUs].<br>Starting in Yocto Kirkstone, populate_sdk will be supported.}}
{{Note|When including some C++ headers, TI's Yocto Dunfell toolchain may not be able to automatically find the full header path.<br>To fix it, the expected paths can be manually added with
<pre>
-I/opt/arago-2021.09/sysroots/aarch64-linux/usr/include/c++/9.2.1 -I/opt/arago-2021.09/sysroots/aarch64-linux/usr/include/c++/9.2.1/aarch64-none-linux-gnu
</pre>
}}
}}

== Install the toolchain/SDK ==
Install the tools by running the resulted script in {{#var:SDK_DIR}}.

E.g.
 $ {{#var:SDK_DIR}}/{{#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}}
</includeonly>