On Thu, Dec 21, 2017 at 6:44 AM, <roup...@gmail.com> wrote: > No I am not talking about the exported function, but the function from the C > function within the preamble, and what about the first part of the question > (scroll up) thank you
Yes, I think I understand. I am saying that if you use //export in the Go program, then the C preamble is linked multiple times, so non-static functions in the preamble will cause multiple definition errors. Again I refer you to https://golang.org/cmd/cgo, where this is documented. Ian > On Thursday, December 21, 2017 at 9:39:07 AM UTC-5, Ian Lance Taylor wrote: >> >> On Thu, Dec 21, 2017 at 6:15 AM, <rou...@gmail.com> wrote: >> > >> > 2 - Do all functions added into the preamble get exported to the header >> > and >> > the shared object that go build creates? >> >> Yes they do, if you use //export, as documented at >> https://golang.org/cmd/cgo. >> >> Ian > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
