I am adding some go components to an openembedded / yocto based project. My question is about a reasonable approach for go building and integration with oe.
I am aware of the work done already to address golang within oe, specifically https://github.com/madisongh/meta-golang/tree/master. This work looks very mature, robust, and well crafted. Though I think the need to use recipe DEPENDS for go dependencies seems a bit redundant, but I understand why that is the case. The go tool provides a fast build capability and seems sufficient during development, particularly with the simplicity of using GOARCH for targeting supported architectures. This is in high contrast to an oe build (bitbake), which is a bit cumbersome and slow, but does a good job for its intended purpose. There's also the issue of vendoring, which I think can be best addressed outside of oe using a normal go workspace, with govendor or other support. So, I am considering an approach which simply uses a normal host development go install with "go build" or "go install" during routine development of go components, and avoids full integration with oe that would use bitbake to initiate building go components. One integrating oe recipe could be used to meld the binary programs generated from a go build into an image for deployment. With this approach, the speed and simplicity of the go tooling are utilized. The build would have two steps. Build the go components, then bitbake the image pulling in the go binary programs already built. Have others taken any similar approach for oe and golang build environments ? Any comments about related oe and go integration ? TIA, Lee -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
