Try this? http://blog.madewithdrew.com/post/statically-linking-c-to-go/
On Sat, Dec 24, 2016 at 6:58 PM Justin Israel
wrote:
>
>
> On Sun, Dec 25, 2016, 2:43 PM James Pettyjohn
> wrote:
>
> Hi Justin,
>
> Thanks for the holiday reply.
>
> The ultimate goal in this was deployment into docker as
On Sun, Dec 25, 2016, 2:43 PM James Pettyjohn wrote:
> Hi Justin,
>
> Thanks for the holiday reply.
>
> The ultimate goal in this was deployment into docker as a self contained
> binary, no dynamic library dependencies and no parent image. The most
> common solution to this I've seen is disable C
Hi Justin,
Thanks for the holiday reply.
The ultimate goal in this was deployment into docker as a self contained
binary, no dynamic library dependencies and no parent image. The most
common solution to this I've seen is disable CGO altogether but with the
libraries I'm using this is not an op
On Sun, Dec 25, 2016 at 9:22 AM James Pettyjohn
wrote:
> I've been looking at a number of articles on statically linking go files
> by disabling CGO, sounds great except I've got a libsass dependency until
> the native libsass is ready.
>
> Can this be in a straightforward manner with go 1.6/1.7
I've been looking at a number of articles on statically linking go files by
disabling CGO, sounds great except I've got a libsass dependency until the
native libsass is ready.
Can this be in a straightforward manner with go 1.6/1.7 on linux (centos)?
--
You received this message because you ar
