Hi all, I'm currently playing with Yocto 1.4, and I have few questions about generated SDKs.
1/ The sysroot seems to be hardcoded in binaries, for instance: $ /opt/poky/1.4.2/sysroots/x86_64-pokysdk-linux/usr/bin/armv6-vfp-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc --print-sysroot /opt/poky/1.4.2/sysroots/armv6-vfp-poky-linux-gnueabi $ ./poky-eglibc-x86_64-arm-toolchain-1.4.1.sh Enter target directory for SDK (default: /opt/poky/1.4.2): /tmp/pokysdk You are about to install the SDK to "/tmp/pokysdk". Proceed[Y/n]? Extracting SDK...done Setting it up...done SDK has been successfully set up and is ready to be used. $ /tmp/pokysdk/sysroots/x86_64-pokysdk-linux/usr/bin/armv6-vfp-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc --print-sysroot /opt/poky/1.4.2/sysroots/armv6-vfp-poky-linux-gnueabi There is a 'relocate_sdk.py', is it meant to replace this path (it does look like it) ? It's replacing some lib-related paths, but the sysroot is kept intact, enforcing the use of --sysroot to use the toolchain. Did I miss something ? 2/ I'm using the 'poky' distribution, which specifies the SDKPATH (in meta-yocto/conf/distro/poky.conf ) as "/opt/${DISTRO}/${SDK_VERSION}". Is there a way to override this without making a new distribution inheriting 'poky' ? I tried to make a new toolchain recipe based on meta-toolchain, and set the value there, but only a small part of the toolchain ends up in that directory (gcc for instance, is compiled with the value set in the poky.conf ). Thanks! Bertrand
_______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto