1b2bf53e82
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] |
||
---|---|---|
.. | ||
build | ||
build-style | ||
check | ||
configure | ||
extract | ||
fetch | ||
install | ||
patch | ||
pkg | ||
setup | ||
setup-subpkg | ||
README |
ENVIRONMENT SHELL SNIPPETS ========================== This directory contains shell files (must not be executable nor contain a shebang) that are read by xbps-src when building source packages. The shell files are read in lexical order (as ordered by shell rules). These files shall set or unset environment variables while building packages. Only files with the `.sh' extension are read, so this file will be simply ignored. The following directories are used to set the order in which the shell snippets should be read by xbps-src: * build-style (to set vars for a specific build_style helper) * setup (before reading template) * setup-subpkg (before running the subpkg <pkgname>_package() function) * fetch (before running fetch phase) * extract (before running extract phase) * configure (before running configure phase) * build (before running build phase) * check (before running check phase) * install (before running install phase) * pkg (before running pkg phase) NOTES ~~~~~ * Symlinks can be created (relative) to make a shell snippet available in multiple phases.