It looks like an issue or bug that GoLang includes the runtime in plugins
so that they cannot be shared. I did
go install -buildmode=shared std
And then I try to compile my plugin as shared:
go build -buildmode=plugin -linkshared /tmp/code_SUM.go# command-line-arguments
runtime.islibrary: mis
On Wednesday, March 22, 2017 at 11:00:24 PM UTC+1, Ian Lance Taylor wrote:
>
> On Wed, Mar 22, 2017 at 3:06 AM, Basile Starynkevitch
> > wrote:
> >
> > First, is Svetlin's golang-sharing-libraries tutorial still exactly
> correct
> > for Go1.8 specifically? Its title Sharing Golang packages
On Wed, Mar 22, 2017 at 3:06 AM, Basile Starynkevitch
wrote:
>
> First, is Svetlin's golang-sharing-libraries tutorial still exactly correct
> for Go1.8 specifically? Its title Sharing Golang packages to C and Go is a
> bit misleading. I just want all my non-main packages to be "shared objects"
>
On Tuesday, March 21, 2017 at 5:59:11 PM UTC+1, Ian Lance Taylor wrote:
Well, there are no Go plugin gurus, and to be honest I'm starting to
> think it was a mistake to let the plugin package into 1.8. I know
> that is not what you want to hear. It's in because the API seems OK,
> but it ha
On Mon, Mar 20, 2017 at 11:53 PM, Basile Starynkevitch
wrote:
>
> On Monday, March 20, 2017 at 8:36:04 AM UTC+1, Basile Starynkevitch wrote:
>>
>> Plugins and packages in Go
>>
>> The package concept is a core concept of Go since every source file
>> belongs to some package (with main being a spec
On Monday, March 20, 2017 at 8:36:04 AM UTC+1, Basile Starynkevitch wrote:
> *Plugins and packages in Go*
>
> The *package* concept is a core concept of Go since every source file belongs
> to some package (with main being a special case) and often imports several
> other ones.
> Practically s
