using sdktool to create toolchains
-
wrote on 4 Sept 2024, 23:35 last edited by
Hi all -
I'm trying to complete the setup of a cross-development system, from a Ubunto host to a Yocto target running on an NXP MXM8P.
I use the sdktool to add the toolchains, but they come up with unknown ABIs. The ABI I use in the command is aarch64-fslc-linux. The complete command looks something like this (adapted from the configure-creator.sh script):
${SDKTOOL} addTC \ --id "ProjectExplorer.ToolChain.Gcc:${BASEID}.g++" \ --name "G++ (${NAME})" \ --path "$(type -p ${CXX})" \ --abi "${ABI}" \ --language Cxx
Any idea what I'm doing wrong here? The added toolchains are in fact good (I've used them to build a program that runs on the target), so this is just kind of cleanup work, but I'd like to get this fixed.
Thanks for any suggestions...
-
wrote on 10 Sept 2024, 01:48 last edited by
It turned out that my string for the ABI was incorrect. The correct string for this toolchain is:
arm-linux-poky-elf-64bit
Though "generic" will work for "poky."
Thanks to all who looked.
-
wrote on 5 Sept 2024, 07:42 last edited by
Mine command for option language uses value 1/2 (respectively for C and C++).
-
Mine command for option language uses value 1/2 (respectively for C and C++).
wrote on 5 Sept 2024, 14:51 last edited by mzimmers 9 May 2024, 14:55@SebastianM I tried that, and it didn't seem to change anything. I'm wondering whether I need to do something with the abi flavor.
I tried adding this line to my command:
${SDKTOOL} addTC \ --id "ProjectExplorer.ToolChain.Gcc:${BASEID}.gcc" \ --name "GCC (${NAME})" \ --path "$(type -p ${CC})" \ --abi "${ABI}" \ --language C --supportedAbis aarch64-fslc-linux
But that didn't help.
-
wrote on 10 Sept 2024, 01:48 last edited by
It turned out that my string for the ABI was incorrect. The correct string for this toolchain is:
arm-linux-poky-elf-64bit
Though "generic" will work for "poky."
Thanks to all who looked.
-
1/4