On Thu, May 9, 2019 at 8:21 AM <grubian.eu...@gmail.com> wrote: > > Thanks for the reply. > Is there any automatic way to build a dynamic library that cgo-package > depends on?
No, I don't think so. > I have the following line in sources of my cgo package(I have the dynamic > library libcl3go.so in cwrap folder): > // #cgo LDFLAGS: -Lcwrap/ -lcl3go > > When I use `go get <my cgo package>` or `go build <external package that uses > the cgo package>` I have got some gotools errors referring the fact that cgo > package is downloaded but not built because of `make` hasn't been run and the > dynamic library hasn't appeared in cwrap folder. > Maybe there is no point of using separate cgo packages depending on dynamic > libraries and I should just include it inside my main package with fully > controlled build mechanisms? If you want to stick to using only the go tool, then I think that is your best approach. Ian -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcVyX%3DbHF6pjX5E2UhiksrnOQjbjEsKPrUA_559khr8dOg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
