Mirror of git.yoctoproject.org/meta-virtualization https://git.enea.com/cgit/linux/meta-virtualization.git/atom?h=hardknott-next 2021-02-10T15:09:25+00:00 2021-02-10T15:09:25+00:00 Bruce Ashfield bruce.ashfield@gmail.com 2021-02-10T15:09:25+00:00 urn:sha1:2a919ae202f659411a8142d3d95bee4c5314fc74 Based on the original recipe from Tim Orling, we introduce a recipe for critools so we can interact diretly with cri based runtimes. We do the normal go manipulations to get this cross building, with the following specific tweak/patch: The build system already knows whether or not we want to use CGO, so we remove the hardcoded variant so our exported environment variable will control the enablement. Since our oe-core go infrastructure insists on both -pie and static builds (for the most part), and that is not recommended by many packages, we end up with errors like: 1.20.0+gitec9e336fd8c21c4bab89a6aed2c4a138c8cfae75/src/import/_output/crictl \ -ldflags '-X github.com/kubernetes-sigs/cri-tools/pkg/version.Version=1.20.0' \ -tags '' \ github.com/kubernetes-sigs/cri-tools/cmd/crictl # github.com/kubernetes-sigs/cri-tools/cmd/crictl cannot find package runtime/cgo (using -importcfg) /work/cortexa72-poky-linux/cri-tools/1.20.0+gitec9e336fd8c21c4bab89a6aed2c4a138c8cfae75-r0/recipe-sysroot-native/usr/lib/aarch64-poky-linux/go/pkg/tool/linux_amd64/link: cannot open file : open : no such file or directory In a similar manner to: https://www.yoctoproject.org/pipermail/meta-virtualization/2019-March/004084.html We introduce '-a -pkgdir dontusecurrentpkgs' to mask/fix the problem, and continue to work towards non-static builds. % root@qemux86-64:~# crictl --version crictl version 1.20.0-dirty Signed-off-by: Tim Orling <ticotimo@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>