[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#808940: Getting an executable



Hi,


Here my summary and notes on https://github.com/hashicorp/terraform/blob/main/.github/CONTRIBUTING.md#terraform-clicore-development-environment

Having `git` and `golang-go` installed.
Have "hello world" for go compiled and run, so you know that it works.

Copy and paste this in your command line terminal:


git clone https://github.com/hashicorp/terraform.git
cd terraform/
go install .
ls -lh $(go env GOPATH)/bin/terraform
$(go env GOPATH)/bin/terraform version
 

This what you can expect as output

stappers@myhost:/usr/src/github
$ git clone https://github.com/hashicorp/terraform.git
Cloning into 'terraform'...
remote: Enumerating objects: 264828, done.
remote: Counting objects: 100% (244/244), done.
remote: Compressing objects: 100% (146/146), done.
remote: Total 264828 (delta 139), reused 174 (delta 94), pack-reused 264584
Receiving objects: 100% (264828/264828), 231.55 MiB | 1.74 MiB/s, done.
Resolving deltas: 100% (164863/164863), done.
stappers@myhost:/usr/src/github
$ cd terraform/
stappers@myhost:/usr/src/github/terraform
$ go install .
       most likely several lines of "downloading something"
       and no additional output
stappers@myhost:/usr/src/github/terraform
$ ls -lh $(go env GOPATH)/bin/terraform
-rwxr-xr-x 1 gs0604 gs0604 82M 19 sep 20:49 /home/stappers/go/bin/terraform
stappers@myhost:/usr/src/github/terraform
$ $(go env GOPATH)/bin/terraform version
Terraform v1.3.0-dev
on linux_amd64
stappers@myhost:/usr/src/github/terraform
$ 


What me did surprise, was how quick / fast the compile is
after the download. I was wondering "Already now a succesfull build?"
In doubt I did another `go install .` which was immediatly finished.
Yes, that build went again fast.

To get the executable "installed" I did:

   
   sudo ln -s /home/stappers/go/bin/terraform /usr/bin/


That symlink will help to be up to date with what is build.



Groeten
Geert Stappers
-- 
Silence is hard to parse


Reply to: