Currently the SDK that is being built, builds successfully but does not contain the vfp arm tuning part included. Overriding the “TARGET_FPU” variable in the local.conf and setting it to *“vfp-neon”*, does reflect in the Build Configuration section, but that still has no difference in the SDK being built. The TARGET_FPU by default is been set to *“hard”. *This was possible in the earlier versions on Yocto though. Setting the CFLAGS in the machine configuration to -mfpu=vfp-neon also has taken no effect.
Would it have something to do with GCC itself? In other words, the SDK currently being built is “ poky-glibc-x86_64-my-meta-toolchain-cortexa8hf-neon-toolchain-2.5.sh” but what is desired is “ poky-glibc-x86_64-my-meta-toolchain-cortexa8hf-vfp-neon-toolchain-2.5.sh” Below is my Build Config, Build Configuration: BB_VERSION = "1.37.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal-4.8" TARGET_SYS = "arm-poky-linux-gnueabi" MACHINE = "arm-cortex-a8" DISTRO = "poky" DISTRO_VERSION = "2.5" TUNE_FEATURES = "arm armv7a vfp neon callconvention-hard cortexa8" TARGET_FPU = "hard" meta-bsp-ti meta meta-poky meta-yocto-bsp meta-my-common meta-oe = "<unknown>:<unknown>" Did something change in the Sumo version of Yocto and Is there any other way of achieving this? Any leads in achieving and helping better understand is appreciated. Thanks! Best Regards, Danny
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto