Yocto Toolchain installation: Difference between revisions
From Variscite Wiki
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{ | {{#if: {{#var:HARDWARE_NAME} | test | {{#vardefine:HARDWARE_NAME|VAR_SOM_MX6}}}} | ||
{{#var:BUILD_FOLDER|$BUILD_FOLDER}} | |||
{{#var:MACHINE_NAME|$MACHINE_NAME}} | |||
{{#var:BUILD_DISTRO|$BUILD_DISTRO}}} | |||
{{#var:$BUILD_SCRIPT|$BUILD_SCRIPT}} | |||
{{#var:BUILD_FOLDER_X11|$BUILD_FOLDER_X11}} | |||
{{#var:TOOLCHAIN_NAME|$TOOLCHAIN_NAME}} | |||
{{#var:TOOLCHAIN_LOCATION|$TOOLCHAIN_LOCATION}} | |||
Assuming you followed steps 1, 3, & 4 of the [[{{#var:HARDWARE_NAME| | {{PageHeader|Yocto toolchain installation for out of Yocto builds}} {{DocImage|category1=Yocto|category2={{#var:HARDWARE_NAME|DART-6UL}}}} __toc__ | ||
Assuming you followed steps 1, 3, & 4 of the [[{{#var:HARDWARE_NAME|DART-6UL}}_Yocto_Morty_Build_Yocto_release|Build Yocto from source code]] guide, as an example of X11 demo image build. Proceed to toolchain build below: | |||
$ cd {{#var:BUILD_FOLDER|~/var-fslc-yocto}} | $ cd {{#var:BUILD_FOLDER|~/var-fslc-yocto}} | ||
$ MACHINE={{#var:MACHINE_NAME|var- | $ MACHINE={{#var:MACHINE_NAME|imx6ul-var-dart}} DISTRO={{#var:BUILD_DISTRO|fslc-x11}} {{#var:$BUILD_SCRIPT|. setup-environment}} {{#var:BUILD_FOLDER_X11|build_x11}} | ||
$ bitbake meta-ide-support | $ bitbake meta-ide-support | ||
$ bitbake meta-toolchain | $ bitbake meta-toolchain | ||
Revision as of 10:14, 3 May 2017
{{#if: test $BUILD_FOLDER $MACHINE_NAME $BUILD_DISTRO} $BUILD_SCRIPT $BUILD_FOLDER_X11 $TOOLCHAIN_NAME $TOOLCHAIN_LOCATION
Yocto toolchain installation for out of Yocto builds
Assuming you followed steps 1, 3, & 4 of the Build Yocto from source code guide, as an example of X11 demo image build. Proceed to toolchain build below:
$ cd ~/var-fslc-yocto $ MACHINE=imx6ul-var-dart DISTRO=fslc-x11 . setup-environment build_x11 $ bitbake meta-ide-support $ bitbake meta-toolchain
The output will be located at tmp/deploy/sdk/. On a 64 bit Ubuntu you will get the following script.
Install the tools by running it:
$ tmp/deploy/sdk/fslc-x11-glibc-x86_64-meta-toolchain-armv7at2hf-neon-toolchain-2.2.1.sh
Reply to all defaults 'y'
The toolchain name depend on your build machine and may change.
Each time you wish to use the toolchain in a new shell session, you need to source the environment setup script:
$ source /opt/fsl-imx-x11/4.1.15-2.0.1/environment-setup-cortexa7hf-neon-poky-linux-gnueabi