Alright, so I played around with this a bit. It would appear that I can
actually get pretty far by just compiling the full standard library as
shared and then compiling the individual packages one at a time in the
proper order. What I am doing is captured in the program in this
repository: ht
Alright, I will take a look. Thanks for the response.
~Parker
On Monday, November 21, 2016 at 7:00:01 PM UTC-5, Ian Lance Taylor wrote:
>
> On Sun, Nov 20, 2016 at 1:22 PM, Parker Evans > wrote:
> >
> > In order to do this kind of thing, do I need to manually figure out
> > dependencies and
On Sun, Nov 20, 2016 at 1:22 PM, Parker Evans wrote:
>
> In order to do this kind of thing, do I need to manually figure out
> dependencies and then setup appropriate linker flags?
Yes, pretty much.
It may help a bit to look at go/build/deps_test.go.
Ian
--
You received this message because y
Hi,
Question about using dynamic libraries on Linux. So I know that creating a
shared .so for the golang standard library can be done via the following
(or some appropriate cross compiling variant):
go install -buildmode=shared -linkshared std
When stripped of debugging information, this proc
