github/rclone
1
Fork 0
mirror of https://github.com/rclone/rclone synced 2024-11-23 00:06:55 +01:00
Code Releases Activity

docs: improve description of make command in install docs

Browse Source
This commit is contained in:
albertony 2022-09-28 08:44:32 +02:00
parent 7fbc928a19
commit 4e078765f9
1 changed files with 13 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
docs/content/install.md
View File

@ -312,9 +312,10 @@ go build -trimpath -ldflags -s -tags cmount
``` ```
Instead of executing the `go build` command directly, you can run it via the Instead of executing the `go build` command directly, you can run it via the
Makefile, which also sets version information and copies the resulting rclone Makefile. It changes the version number suffix from "-DEV" to "-beta" and
executable into your GOPATH bin folder (`$(go env GOPATH)/bin`, which appends commit details. It also copies the resulting rclone executable into
corresponds to `~/go/bin/rclone` by default). your GOPATH bin folder (`$(go env GOPATH)/bin`, which corresponds to
`~/go/bin/rclone` by default).
``` ```
make make
@ -326,7 +327,15 @@ To include mount command on macOS and Windows with Makefile build:
make GOTAGS=cmount make GOTAGS=cmount
``` ```
As an alternative you can download the source, build and install rclone in one There are other make targets that can be used for more advanced builds,
such as cross-compiling for all supported os/architectures, embedding
icon and version info resources into windows executable, and packaging
results into release artifacts.
See [Makefile](https://github.com/rclone/rclone/blob/master/Makefile)
and [cross-compile.go](https://github.com/rclone/rclone/blob/master/bin/cross-compile.go)
for details.
Another alternative is to download the source, build and install rclone in one
operation, as a regular Go package. The source will be stored it in the Go operation, as a regular Go package. The source will be stored it in the Go
module cache, and the resulting executable will be in your GOPATH bin folder module cache, and the resulting executable will be in your GOPATH bin folder
(`$(go env GOPATH)/bin`, which corresponds to `~/go/bin/rclone` by default). (`$(go env GOPATH)/bin`, which corresponds to `~/go/bin/rclone` by default).