Aagh! I misunderstood the question. Apologies for that. There may still be a grain of usefulness in my answer. There are limits to the complexity of the C code that you can call with cgo. (It’s even worse if you are calling C++, as I was.) You can magic away a lot of those problems by writing an extra layer of C that hides the complexities.
However, this probably involves having make around to bind everything together. I agree that this is a nuisance, because your user may not have make, particularly if they are using Windows. There is a version of gnu make available for that, but using it just led me to a different world of pain. Have you considered having two separate pieces of software, one in C and one in Go and linking them together with grpc? That would allow you to ship your solution as two binaries. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
