You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
defaultCC is written by 'cmd/dist' into cmd/go/zdefaultcc.go and cmd/cgo/zdefaultcc.go, but neither of those locations can be used because (a) they are commands (b) the value is not exported.
Could defaultCC be written as DefaultCC into go/build so it can be reused by other tools that need access to the C compiler that the Go install was installed with.
The text was updated successfully, but these errors were encountered:
Shell out to "go env CC" or "go env CXX"?
This also handles the CC/CXX environment variable.
defaultCC mechanism is bad fit for the go tool as it only handles one
platform, but I'd it to be able to handle multiple platforms.
Simply adding DefaultCC is the wrong approach because in principle we want to have a different default compiler for different GOARCH/GOOS values. Closing this out, but reopen if you want an approach different from calling "go env CC".
Simply adding DefaultCC is the wrong approach because in principle we want
to have a different default compiler for different GOARCH/GOOS values.
Closing this out, but reopen if you want an approach different from calling
"go env CC".
—
Reply to this email directly or view it on GitHub #10916 (comment).
defaultCC
is written by 'cmd/dist' intocmd/go/zdefaultcc.go
andcmd/cgo/zdefaultcc.go
, but neither of those locations can be used because (a) they are commands (b) the value is not exported.Could
defaultCC
be written asDefaultCC
intogo/build
so it can be reused by other tools that need access to the C compiler that the Go install was installed with.The text was updated successfully, but these errors were encountered: