meta-toolchain question
When I build the meta-toolchain for my armv5te target, I see some confusing paths. For example, why is the environment script named
/opt/poky/1.00+snapshot/environment-setup-armv5te-poky-linux-gnueabi
but the sysroot is named
/opt/poky/1.00+snapshot/sysroots/arm-poky-linux-gnueabi
Why isn't it
/opt/poky/1.00+snapshot/sysroots/armv5te-poky-linux-gnueabi
I even see some stranger paths, like these
/opt/poky/1.00+snapshot/sysroots/i686-pokysdk-linux/usr/lib/armv5te-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi
I would think it should be armv5te-poky-linux-gnueabi everywhere.
If I wanted to also have a meta-toolchain for armv7a, there would be a clash since they both use the same sysroots.
Note: I sort of asked this question yesterday and the answer was "use ADT". I don't see that ADT will solve this and I also find ADT much to heavyweight for my customers who just want a simple toolchain that matches their Poky-built system.
Thanks
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------