8291bc7793
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> |
||
|---|---|---|
| .. | ||
| artifact_info | ||
| Config.in | ||
| device_type | ||
| mender.conf | ||
| mender.hash | ||
| mender.mk | ||
| mender.service | ||
| readme.txt | ||
| S42mender | ||
| server.crt | ||
=== Notes on using Mender on Buildroot ====================================== Default configurations files ---------------------------- Buildroot comes with a default artifact_info and device_type configuration files in /etc/mender. They contain default values, and thus they should be overridden on a production system. The simplest way to do it is to change these files in an overlay or in a post build script. Configuring mender with certificates ------------------------------------ Mender uses TLS to communicate with the management server, and if you use a CA-signed certificate on the server, you should select the ca-certificates package otherwise it doesn't work.