3 ms·
Or for languages with no such non-language-native dependencies, like Go, where I've found it to be piece of cake (and I've never ever tried it for C).
by coldtea 6y ago
Or for languages with no such non-language-native dependencies, like Go, where I've found it to be piece of cake (and I've never ever tried it for C).
- pjmlp 6y agoThat only works for pure Go code (no use of cgo) and for Go libraries that don't call into OS APIs.
- est31 6y agoYou can absolutely call into OS APIs, as that's what the Go implementation does to interact with the OS in the first place. It also uses cgo internally for that task. https://github.com/golang/go/blob/2a029b3f26169be7c89cb2cdcc3db4b5d097a8b8/src/runtime/os_windows.go https://github.com/golang/go/blob/2a029b3f26169be7c89cb2cdcc...
- pjmlp 6y agoRight, now try to actually use it. Specially missing entries from that list.
- est31 6y agoWhat do you mean? You use this when you use the builtin os package of Go. https://golang.org/pkg/os/ https://golang.org/pkg/os/
- pjmlp 6y agoNow try to use that, to call these from a Linux compiled executable, https://docs.microsoft.com/en-us/windows/win32/api/ https://docs.microsoft.com/en-us/windows/win32/api/
- coldtea 6y ago>That only works for pure Go code (no use of cgo) Yes. I never cared for cgo, and I'd say most don't. >and for Go libraries that don't call into OS APIs. Or that have those APIs wrapped for different conventions. So? This still leaves billions of possible apps, and thousands of existing ones...