<div dir="ltr">Hi,<div><br></div><div>I've successfully built a Canadian-cross SDK using the meta-mingw layer. Very nice!</div><div><br></div><div>Because the layer lobotomizes the SDK_PACKAGING_FUNC when ${SDKMACHINE} is set to a MinGW host, though, the resulting SDK is not encapsulated into the self-extracting tarball and the corresponding relocation logic (<span style="font-family:monospace,monospace">relocate_sdk.py</span>Â and so forth) is omitted.</div><div><br></div><div>Any suggestions on how to do the last-mile work to use the SDK on Windows? Or perhaps nothing is needed at all, except adjusting the prefixes built into <font face="monospace, monospace">environment-setup-<arch></font>? Although that would be nice, I think at least some installation-time adjustment is necessary though; when I do:</div><div><br></div><div><font face="monospace, monospace">Â Â arm-poky-linux-gnueabi-gcc -o foo foo.c --sysroot=d:/projects/yocto-sdk/sysroots/cortexa15t2hf-vfp-neon-poky-linux-gnueabi</font></div><div><br></div><div>, the following happens during linking:</div><div><br></div><div><font face="monospace, monospace">Â Â ld.exe: cannot find /lib/libc.so.6 inside d:/projects/yocto-sdk/sysroots/cortexa15t2hf-vfp-neon-poky-linux-gnueabi</font></div><div><br></div><div>Cheers,</div><div>Matt</div></div>