summaryrefslogtreecommitdiffstats
path: root/recipes-devtools/go/go-build_git.bb
Commit message (Collapse)AuthorAgeFilesLines
* global: convert github SRC_URIs to use https protocolBruce Ashfield2021-11-021-1/+1
| | | | | | | | | | | github is removing git:// access, and fetches will start experiencing interruptions in service, and eventually will fail completely. bitbake will also begin to warn on github src_uri's that don't use https. So we convert the meta-virt instances to use protocol=https (done using the oe-core contrib conversion script) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* global: overrides syntax conversionBruce Ashfield2021-08-021-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | OEcore/bitbake are moving to use the clearer ":" as an overrides separator. This is pass one of updating the meta-virt recipes to use that syntax. This has only been minimally build/runtime tested, more changes will be required for missed overrides, or incorrect conversions Note: A recent bitbake is required: commit 75fad23fc06c008a03414a1fc288a8614c6af9ca Author: Richard Purdie <richard.purdie@linuxfoundation.org> Date: Sun Jul 18 12:59:15 2021 +0100 bitbake: data_smart/parse: Allow ':' characters in variable/function names It is becomming increasingly clear we need to find a way to show what is/is not an override in our syntax. We need to do this in a way which is clear to users, readable and in a way we can transition to. The most effective way I've found to this is to use the ":" charater to directly replace "_" where an override is being specified. This includes "append", "prepend" and "remove" which are effectively special override directives. This patch simply adds the character to the parser so bitbake accepts the value but maps it back to "_" internally so there is no behaviour change. This change is simple enough it could potentially be backported to older version of bitbake meaning layers using the new syntax/markup could work with older releases. Even if other no other changes are accepted at this time and we don't backport, it does set us on a path where at some point in future we could require a more explict syntax. I've tested this patch by converting oe-core/meta-yocto to the new syntax for overrides (9000+ changes) and then seeing that builds continue to work with this patch. (Bitbake rev: 0dbbb4547cb2570d2ce607e9a53459df3c0ac284) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* go-build: export GO111MODULE=offBruce Ashfield2021-03-261-0/+1
| | | | | | | We aren't setup for go module builds, so we need to disable it in the go-build recipe. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* go-build: refresh to latest runX commitBruce Ashfield2020-09-161-8/+1
| | | | | | | | | | Updating the go-build recipe to use the latest runX commit and sync with the main recipe. We also no longer need runc and recvtty so they are dropped from the recipe. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* go-build: fix build with new go-binary bootstrapped toolchainBruce Ashfield2020-08-071-2/+16
| | | | | | | We need to be more explicity in our exports and use of 'go' to build properly with the new binary bootstrapped go toolchain. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* go-build_git.bb: go-build: set GO_PARALLEL_BUILD to default valueChandana kalluri2020-04-081-0/+1
| | | | | | | | | | | | Set GO_PARALLEL_BUILD to default to prevent the following error: failed to create new OS thread (have 13 already; errno=11) runtime: may need to increase max user processes (ulimit -u) fatal error: newosproc Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@xilinx.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* go-build: Set up dependencies and GOPATH before do_compileChandana kalluri2020-04-081-0/+6
| | | | | | | | | | | | | | | go-build recipe depends on runc source and during compilation tries to run the command: go get github.com/opencontainers/runc. This is incorrect as a source fetch shouldn't occur during compilation. Also, even after a fetch occurs during compilation, the go build path GOPATH points to the incorrect path hence the runc source is never found. Fetch the opencontainers/runc source and create links in the correct GOPATH before compilation for a successful build. Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* go-build: drop distro_features_checkDaniel Dragomir2020-03-181-1/+1
| | | | | | | | Replace distro_features_check bbclass which is deprecated, with features_check bbclass. Signed-off-by: Daniel Dragomir <Daniel.Dragomir@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* go-build_git.bb: go-build recipe to manage go build dependencies for runXSai Hari Chandana Kalluri2020-03-151-0/+43
go-build_git recipe manages go build dependencies for runX. This is used to support a console access for runX. Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>