Re: [go-nuts] best practices for gccgo and external packages

2018-04-24 Thread Ian Lance Taylor
On Tue, Apr 24, 2018 at 10:15 AM, Philip Brown wrote: > > On Tuesday, April 24, 2018 at 6:56:21 AM UTC-7, Ian Lance Taylor wrote: >> >> >> Sorry, you're quite right. I completely forgot that >> -buildmode=archive is the default for a non-main package. >> > > Okay, so just to close the loop on inf

Re: [go-nuts] best practices for gccgo and external packages

2018-04-24 Thread Philip Brown
On Tuesday, April 24, 2018 at 6:56:21 AM UTC-7, Ian Lance Taylor wrote: > > > Sorry, you're quite right. I completely forgot that > -buildmode=archive is the default for a non-main package. > > Okay, so just to close the loop on information sharing, I think you are saying that -buildmode=arch

Re: [go-nuts] best practices for gccgo and external packages

2018-04-24 Thread Ian Lance Taylor
On Mon, Apr 23, 2018 at 10:32 PM, Philip Brown wrote: > On Mon, Apr 23, 2018 at 9:23 PM, Ian Lance Taylor wrote: >> >> >> There is no -buildmode=archive. Using -buildmode=c-archive should >> work if that is what you want to do. >> > > ORLLY? :-} > > $ go help buildmode > The 'go build' and 'go i

Re: [go-nuts] best practices for gccgo and external packages

2018-04-23 Thread Philip Brown
On Mon, Apr 23, 2018 at 9:23 PM, Ian Lance Taylor wrote: > > > There is no -buildmode=archive. Using -buildmode=c-archive should > work if that is what you want to do. > ORLLY? :-} $ go help buildmode The 'go build' and 'go install' commands take a -buildmode argument which indicates which kind

Re: [go-nuts] best practices for gccgo and external packages

2018-04-23 Thread Ian Lance Taylor
On Mon, Apr 23, 2018 at 6:40 PM, Philip Brown wrote: > > the docs at > https://golang.org/doc/install/gccgo > seem to mention how to use packages for your own code, but dont mention how > to use third party packages. > > In other words, in situations where you would normally do > > go get github.o