aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorGravatar Angelo Compagnucci <angelo@amarulasolutions.com>2019-02-06 14:23:57 +0100
committerGravatar Thomas Petazzoni <thomas.petazzoni@bootlin.com>2019-03-17 17:20:53 +0100
commit8291bc77930a5ef87f98d1ff97c486dddfcdb244 (patch)
tree7aee7df98890d33ed052e0a1a625cb2b4f98f61f /docs
parent65895f36eea0139c3d590cd5982be5504b2de9ce (diff)
downloadbuildroot-8291bc77930a5ef87f98d1ff97c486dddfcdb244.tar.gz
buildroot-8291bc77930a5ef87f98d1ff97c486dddfcdb244.tar.bz2
package/go: rename BR2_PACKAGE_HOST_GO_{ARCH_SUPPORTS,CGO_LINKING_SUPPORTS}
The hidden Config.in option BR2_PACKAGE_HOST_GO_ARCH_SUPPORTS name is not very clear as to whether it says whether Go is available for the target architecture or the host architecture. Until now, this was fine since there was support for host Go packages. But as we are about to introduce support for building host Go packages, we need to clarify the meaning of BR2_PACKAGE_HOST_GO_ARCH_SUPPORTS. Since it says whether the target architecture has support for Go or not, we rename it to BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS. And since BR2_PACKAGE_HOST_GO_CGO_LINKING_SUPPORTS is tightly related, we rename it to BR2_PACKAGE_HOST_GO_TARGET_CGO_LINKING_SUPPORTS. Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com> Tested-by: Adam Duskett <aduskett@gmail.com> [Thomas: entirely rewrite commit log] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/manual/adding-packages-golang.txt8
1 files changed, 5 insertions, 3 deletions
diff --git a/docs/manual/adding-packages-golang.txt b/docs/manual/adding-packages-golang.txt
index efcf696867..ae90eb7d4f 100644
--- a/docs/manual/adding-packages-golang.txt
+++ b/docs/manual/adding-packages-golang.txt
@@ -45,9 +45,11 @@ built.
==== +golang-package+ reference
In their +Config.in+ file, packages using the +golang-package+
-infrastructure should depend on +BR2_PACKAGE_HOST_GO_ARCH_SUPPORTS+
-and +BR2_PACKAGE_HOST_GO_CGO_LINKING_SUPPORTS+ because Buildroot will
-automatically add a dependency on +host-go+ to such packages.
+infrastructure should depend on +BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS+
+because Buildroot will automatically add a dependency on +host-go+
+to such packages.
+If you need CGO support in your package, you must add a dependency on
++BR2_PACKAGE_HOST_GO_TARGET_CGO_LINKING_SUPPORTS+.
The main macro of the Go package infrastructure is
+golang-package+. It is similar to the +generic-package+ macro. Only