Golang 1.5 presents an interesting change to how this layer will work. I plan to make the following changes to handle it.
1) I cannot currently consider the gccgo environment as production ready without more complete testing. There are already lots of oddities that have to be worked around due to stripping. The runtime is also falling behind now that the mainline go runtime is completely written in go. Perhaps this will change in the future. Until then, I will be making gccgo be a secondary class and will default to building with golang directly. You can pick which toolchain to use by which class a recipe inherits from.
2) The golang-cross recipe will require a working go1.4 or greater to be installed on the host computer in order to compile go1.5. I think it is silly to try and build a bootstrapping system into yocto when that requirement is simple enough to meet.
Golang 1.5 presents an interesting change to how this layer will work. I plan to make the following changes to handle it.
1) I cannot currently consider the gccgo environment as production ready without more complete testing. There are already lots of oddities that have to be worked around due to stripping. The runtime is also falling behind now that the mainline go runtime is completely written in go. Perhaps this will change in the future. Until then, I will be making gccgo be a secondary class and will default to building with golang directly. You can pick which toolchain to use by which class a recipe inherits from.
2) The golang-cross recipe will require a working go1.4 or greater to be installed on the host computer in order to compile go1.5. I think it is silly to try and build a bootstrapping system into yocto when that requirement is simple enough to meet.