Hi, I think I would leave the toolchain artifact as is, but just surround the the 'cp' with an 'if' statement. E.g.,: if [ -e <path-to-x86-toolchain> ]; then cp <cp-args> <path-to-x86-toolchain> <destination>; fi; if [ -e <path-to-x86_64-toolchain> ]; then cp <cp-args> <path-to-x86_64-toolchain> <destination>; fi;
-Bill On Sat, Oct 8, 2016 at 2:52 PM, <gm...@reliableembeddedsystems.com> wrote: > Hi, > > On 2016-10-08 09:28, Bill Randle wrote: >> >> >> All the "standard" build configs produce both x86 and x86_64 >> toolchains - which makes sense, since it's not known what build host >> the user is using and the AB needs to show both are buildable. In your >> case, you know you have an x86_64 machine and don't want to bother >> building for x86, so, it's seems like the thing to do is check for the >> existence of a build package (x86 or x86_64) before attempting the >> copy. >> > > That's what I thought as well at first. So I introduced new toolchain > artifacts like toolchain_x86_64 and toolchain_i686 where I did only the > relevant thing in the relevant branch. > It did not solve my problem. > > Regards, > > Robert -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto