[go-nuts] Re: Hide Golang Code from Exported package

2022-12-23 Thread Jason E. Aten
I've made Windows DLLs work with Go, so I can be done, but I would strongly suggest that you avoid it. Windows applications expect to be able to unload their DLLs, and you can never do that with Go. There are work arounds, (search this form for my previous posts), but they are ugly and fragile. So

[go-nuts] Re: Hide Golang Code from Exported package

2022-12-14 Thread neeraj singhi
Hi is there another way as we have to package it as a dll or a lib . But whenever we try using syscall with dll it fails with "bad sweepgen in refill" Is there any other way where we font create a new executable thanks On Monday, December 12, 2022 at 1:34:23 PM UTC+5:30 Brian Candler wrote: >

[go-nuts] Re: Hide Golang Code from Exported package

2022-12-12 Thread Brian Candler
Distribute your library as a grpc server. https://github.com/hashicorp/go-plugin On Monday, 12 December 2022 at 07:56:52 UTC nsing...@gmail.com wrote: > Actually i need to share it as an sdk. So any way i can share > > On Thursday, December 8, 2022 at 1:13:17 PM UTC+5:30 marc...@gmail.com > wrot

[go-nuts] Re: Hide Golang Code from Exported package

2022-12-11 Thread neeraj singhi
Actually i need to share it as an sdk. So any way i can share On Thursday, December 8, 2022 at 1:13:17 PM UTC+5:30 marc...@gmail.com wrote: > if you produce an executable, nobody sees the actual Go code. > build it with: > go build -ldflags "-s -w" > > or you could try to obfuscate it: > https:/

[go-nuts] Re: Hide Golang Code from Exported package

2022-12-07 Thread Marcello H
if you produce an executable, nobody sees the actual Go code. build it with: go build -ldflags "-s -w" or you could try to obfuscate it: https://github.com/burrowers/garble or you can make a self-extracting executable Op woensdag 7 december 2022 om 19:09:31 UTC+1 schreef nsing...@gmail.com: >