Hi, I have an existing project existing of a "library" creating a wrapper to "C" using "go install" and on a different place multiple "executable's" everything glue together using the *GOPATH* technology. NOW I start using the new "module" technology.
Library: 1. I create with "mod init *pkgname*" my module 2. I build my library use both "go install" or "go build" and the build is done but NO final "pkg/*/*pkgname*.a" file is created → why? 3. If I use "go build -o *pkgname*.a ." I get my "*pkgname*.a" and I can place it everywhere I want. Executable: 1. I create with "mod init example" a module in the directory using multiple "main" go files 2. NOW I have the problem to refer my local library WITHOUT using the " *GOPATH*" 3. In my "main" files I have "import (. *pkgname* ...)" but this does not works. Expectation: my expectation was that the library "*pkgname*" after build is available in the global module cache (because pkg/.../*pkgname*.a was NOT written :-) but "go list all" has NOT my package Question: HOW do I refer to my local module-package from an existing executable ? →thanks for help. -- 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/1c4940bf-ef59-46e1-b77d-a2c05f117a95%40googlegroups.com.
