Yocto Toolchain installation: Difference between revisions

From Variscite Wiki
No edit summary
No edit summary
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<!-- Set release according to "release" parameter in URL and use RELEASE_MORTY_V1.0_DART-6UL as default
<!-- Set release according to "release" parameter in URL and use RELEASE_MORTY_V1.0_DART-6UL as default
--> {{#vardefine:RELEASE_PARAM|{{#urlget:release}}}} <!--
--> {{#vardefine:RELEASE_PARAM|{{#urlget:release|RELEASE_MORTY_V1.0_DART-6UL}}}} <!--
--> {{#lst:Yocto_Platform_Customization|{{#var:RELEASE_PARAM|RELEASE_MORTY_V1.0_DART-6UL}}}} <!--
--> {{#lst:Yocto_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 }} }} <!--
-->{{#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}}}} }} }}<!--
--> {{PageHeader|Yocto toolchain installation for out of Yocto builds}} {{DocImage|category1=Yocto|category2={{#var:HARDWARE_NAME}}}} __toc__
--> {{PageHeader|Yocto toolchain installation for out of Yocto builds}} {{DocImage|category1=Yocto|category2={{#var:HARDWARE_NAME}}}} __toc__


Line 9: Line 12:


== Build a toolchain ==
== Build a toolchain ==
$ cd {{#var:BUILD_FOLDER}}
{{#lst:Yocto_Platform_Customization|YOCTO_ENV_SETUP_X}}
$ 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
  $ bitbake meta-toolchain
  $ bitbake meta-toolchain{{#ifeq: {{#var:BUILD_FOLDER}}|~/var-b2qt|-b2qt-embedded-qt5-sdk|}}


== Build a complete 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.
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}}
{{#lst:Yocto_Platform_Customization|YOCTO_ENV_SETUP_X}}
$ 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 {{#var:DEFAULT_IMAGE_BB_NAME}} image:
  $ bitbake -c populate_sdk fsl-image-gui
  $ 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.}}
{{Note|The SDK should match the rootfs image on the target, otherwise you may experience difficulties when trying to debug application failures.}}


Line 28: Line 30:


E.g.
E.g.
  $ tmp/deploy/sdk/{{#ifeq: {{#var:SOC_SERIES}}|imx8|{{#var:TOOLCHAIN_INSTALL_XWAYLAND_NAME}}|{{#var:TOOLCHAIN_INSTALL_X11_NAME}}}}
  $ 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>
Note: The toolchain/script name depends on your build machine and the bitbaked image/recipe, and may change.<br>
<br>
<br>
Accept all the default options, and at the end of the installation you should see the following:
Accept all the default options, and at the end of the installation you should see the following:

Revision as of 15:44, 1 March 2021

Yocto toolchain installation for out of Yocto builds

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
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