3 ms·
That's not even true. You can use the compiler and linkers to your hearts content. What you meant to say was, their braindead idea was that if you want to be a
by drivebyacct2 14y ago
That's not even true. You can use the compiler and linkers to your hearts content.
What you meant to say was, their braindead idea was that if you want to be able to trivially use ANY go program or library on GitHub, you can use $GOPATH and the go tool [1] and not fuck around with autotools and makefiles.
If you're into S&M, no one is stopping you from using the core pieces of the `go` tool by hand.
[1]: ALL of my code can be download, built and run with: `go get github.com/myname/myproject; myproject` (I have $GOPATH/bin on my path)
- Mooby 14y agoI'm not talking about gc. I'm talking about go. You know, the program which is extensively marketed as the only program which is required to build and run Go programs, and the standard and default way to deal with Go, from installing third-party packages and running your program through an interpreter. Referring to gc makes as much sense as referring to gccgo.
- drivebyacct2 14y agoWhat do you want? You don't want to use the `go` tool, DON'T USE IT. Seriously, the alternative that you are implying that you want is already available to you.
- agentS 14y agoNot sure if you know this (or anything about Go), but the go tool just uses a bunch of other programs to accomplish what it does (including git, bzr, the compiler and the linker). If you want to do your own thing, you're free to ignore the rest of the community in this respect, and create your own build mechanism. In fact, if you pass the "-x" flag to the go tool, you can even see how its accomplishing what its accomplishing; which might help you write this better build tool.