/src/<companyname>/folder1 /src/<companyname>/folder2 /src/<companyname>/folder3 ...
Everything works fine with go build ./src/<companyname>/... I've recently added a module (/src/<companyname>/folder4) which calls go code from c and and this go folder is built with: go build --buildmode=c-archive -o libgolang.a I'm not sure what the best practices are here and have the following questions: - Should I exclude /src/<companyname>/folder4 from being built automatically when I run ./src/<companyname>/... If I do exclude it, how would I do it? - Where should libgolang.a be stored? -- 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.
