I am working on setting up NTPsec's build system to properly handle Go code, and can only find limited information of the preferred way of structuring the directory tree.
Forcing the entire project into GOPATH would be sloppy and a giant kluge all around. Placing the go code in a folder with no special structure (as we currently do with Python), and then using relative module paths appears to work in testing. However from what I gather relative module paths are a deeply unkosher feature that should not be depended on. The only other way I see is simply to replicate a GOPATH directory structure within the project and have the build tools define a custom GOPATH. This forces a somewhat clunky directory structure on the project with an otherwise unneeded src/ directory. A possible workaround would be to structure the code as with Python, then have the build system copy the files into a src/ directory under build/ and run with that GOPATH. -- 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.
