snailed
/
void-packages
2
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Activity
void-packages/common/environment/build-style/go.sh

42 lines
1.2 KiB
Bash
Raw Normal View History

environment/build-style/go: check for empty hostmakedepends
2020-04-17 04:58:25 +02:00
if [ -z "$hostmakedepends" -o "${hostmakedepends##*gcc-go-tools*}" ]; then
build-style/go: allow usage with gccgo compiler This checks if gcc-go-tools have been specified in host deps and if so, use gccgo to build (gcc-go-tools conflicts with go). Also, since gccgo is not a multi-compiler, we need to override GCCGO to get cross-builds. The gccgo for target is always installed, as it's a part of our cross-toolchains. [ci skip]
2019-11-11 03:03:14 +01:00
# gc compiler
if [ -z "$archs" ]; then
archs="aarch64* armv[567]* i686* x86_64* ppc64le*"
fi
hostmakedepends+=" go"
nopie=yes
else
# gccgo compiler
if [ "$CROSS_BUILD" ]; then
# target compiler to use; otherwise it'll just call gccgo
export GCCGO="${XBPS_CROSS_TRIPLET}-gccgo"
fi
environment/build-style/go.sh: specify a default set of archs This is necessary so that crossbuilds to unsupported architectures are not actually attempted. There is a default archs set which covers all architectures supported by the official compiler, and setting it in the template can be used to restrict it more. Also, add missing GOARCHs. These are irrelevant to whether we can currently build for that arch or not. Just keep it around as a list of potential archs to support. These are taken from gccgo, and in case support for anything is added in the official compiler, they should match.
2019-11-11 03:03:14 +01:00
fi
New build_style: go
2015-02-21 13:38:37 +01:00
nostrip=yes
set Go env vars in environment This way, a template can overwrite do_build but still have good defaults for GOPATH, GOARCH and GOARM.
2015-02-21 14:34:03 +01:00
case "$XBPS_TARGET_MACHINE" in
build-style/go.sh: enable aarch64.
2016-09-16 22:26:56 +02:00
aarch64*) export GOARCH=arm64;;
environment/build-style/go.sh: specify a default set of archs This is necessary so that crossbuilds to unsupported architectures are not actually attempted. There is a default archs set which covers all architectures supported by the official compiler, and setting it in the template can be used to restrict it more. Also, add missing GOARCHs. These are irrelevant to whether we can currently build for that arch or not. Just keep it around as a list of potential archs to support. These are taken from gccgo, and in case support for anything is added in the official compiler, they should match.
2019-11-11 03:03:14 +01:00
armv5*) export GOARCH=arm; export GOARM=5;;
set Go env vars in environment This way, a template can overwrite do_build but still have good defaults for GOPATH, GOARCH and GOARM.
2015-02-21 14:34:03 +01:00
armv6*) export GOARCH=arm; export GOARM=6;;
armv7*) export GOARCH=arm; export GOARM=7;;
i686*) export GOARCH=386;;
x86_64*) export GOARCH=amd64;;
common: add ppc64 build profiles and other ppc64 bits This adds the build profiles for ppc64 targets as well as modifications in other parts of the infra. These targets are supported: - ppc64le (glibc little endian elfv2) - ppc64le-musl (musl little endian) - ppc64-musl (musl big endian) ELFv1 targets are explicitly not supported at this point. Big endian musl supports ppc 970 or newer, while little endian targets are set to a generic powerpc64le which effectively means POWER8 and newer. Tuning is always set for POWER9, which is the most likely target hardware. We also make sure AltiVec is always on, because it is supported on all hardware we target. [ci skip]
2019-01-01 00:24:00 +01:00
ppc64le*) export GOARCH=ppc64le;;
ppc64*) export GOARCH=ppc64;;
environment/build-style/go.sh: specify a default set of archs This is necessary so that crossbuilds to unsupported architectures are not actually attempted. There is a default archs set which covers all architectures supported by the official compiler, and setting it in the template can be used to restrict it more. Also, add missing GOARCHs. These are irrelevant to whether we can currently build for that arch or not. Just keep it around as a list of potential archs to support. These are taken from gccgo, and in case support for anything is added in the official compiler, they should match.
2019-11-11 03:03:14 +01:00
ppc*) export GOARCH=ppc;;
mipsel*) export GOARCH=mipsle;;
mips*) export GOARCH=mips;;
set Go env vars in environment This way, a template can overwrite do_build but still have good defaults for GOPATH, GOARCH and GOARM.
2015-02-21 14:34:03 +01:00
esac
export GOPATH="${wrksrc}/_build-${pkgname}-xbps"
go build style: move GOPATH creation to do_configure()
2017-11-24 23:05:29 +01:00
GOSRCPATH="${GOPATH}/src/${go_import_path}"
build-style/go: support cross-compilation with cgo
2015-09-04 02:18:57 +02:00
export CGO_CFLAGS="$CFLAGS"
export CGO_CPPFLAGS="$CPPFLAGS"
export CGO_CXXFLAGS="$CXXFLAGS"
export CGO_LDFLAGS="$LDFLAGS"
export CGO_ENABLED=1
build style go.sh: split gocache for glibc/muslc Closes: #2542 Signed-off-by: Jürgen Buchmüller <pullmoll@t-online.de>
2018-09-11 12:38:46 +02:00
case "$XBPS_TARGET_MACHINE" in
*-musl) export GOCACHE="${XBPS_HOSTDIR}/gocache-muslc" ;;
*) export GOCACHE="${XBPS_HOSTDIR}/gocache-glibc" ;;
esac