Template:Yocto Toolchain installation AM62: Difference between revisions
From Variscite Wiki
| Line 24: | Line 24: | ||
{{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|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 | {{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 | ||
-I{{#var:TOOLCHAIN_TARGET_SYSROOT_LOCATION}}/usr/include/c++/ | -I{{#var:TOOLCHAIN_TARGET_SYSROOT_LOCATION}}/usr/include/c++/{{#var:TOOLCHAIN_GCC_VER}} -I{{#var:TOOLCHAIN_TARGET_SYSROOT_LOCATION}}/usr/include/c++/{{#var:TOOLCHAIN_GCC_VER}}/{{#var:TOOLCHAIN_TYPE}} | ||
}} | }} | ||
}} | }} | ||