I love the design and actual use of acmetool but would like to include it into our ports tree by building from source. That would also help us cross-compile for Raspberry Pi.
Your otherwise excellent documentation just says "building from source is easy". Go is of course new territory to some, but while building v0.2.1 I am also encountering:
- References to
git.devever.net/hlandau/acmetool which does not exist
- An import path from
github.com/hlandau/acmetool/cli that I could not get to work by setting $GOROOT and/or $GOPATH
- Apparent assumption that the source is in a directory named
src and built with go build src/main.go so that a plain import cli can work
- Failure to find standard library utilities, also after setting
$GOPATH to either packages or sources
What I'm saying is that there seem to be assumptions about the environment in which the package is built that are useful to describe. Part of this may be my lack of experience programming with Go, but not everything, I suppose.
Could you please describe the building process? I would be happy to test-ride any text you might churn out.
I love the design and actual use of
acmetoolbut would like to include it into our ports tree by building from source. That would also help us cross-compile for Raspberry Pi.Your otherwise excellent documentation just says "building from source is easy". Go is of course new territory to some, but while building
v0.2.1I am also encountering:git.devever.net/hlandau/acmetoolwhich does not existgithub.com/hlandau/acmetool/clithat I could not get to work by setting$GOROOTand/or$GOPATHsrcand built withgo build src/main.goso that a plainimport clican work$GOPATHto either packages or sourcesWhat I'm saying is that there seem to be assumptions about the environment in which the package is built that are useful to describe. Part of this may be my lack of experience programming with Go, but not everything, I suppose.
Could you please describe the building process? I would be happy to test-ride any text you might churn out.