I'm actively using meta-golang for development and continuing to add features as I find them necessary. If anyone has suggestions on what would be useful as a developer of embedded go applications, let me know.
Specifically, I am most interested on input for what would be useful configuration variables to have available for golang based recipes: * Ways to request how to breakdown a golang project into combinations of shared libraries, static libraries, and executables. * Being able to define which golang packages are to be placed into libraries vs statically linked into the executables. If someone manages to get this properly integrated into yocto, I would be happy to move my development directly to the project. -Chris On Oct 30, 2014, at 5:47 AM, Maciej Borzecki <maciej.borze...@open-rnd.pl> wrote: > There's also https://github.com/digitallumens/meta-golang > > Based on that I've prepped some patches not long ago that integrate go into > OE-core base on what Chris did in meta-golang. The patches are for both meta-- > golang and OE-core. OE-core piece enables Go GCC frontend and libgo same way > as Fortran or Java is handled. Also, Chris has already defined a usable > golang.bbclass that handles gccgo build for you. So far it seems to work with > some simple use cases on BeagleBone Black and Raspberry. > > If there's interest I can update the patches to current master and post them > to the list. -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
