Fails to build with go mod vendor

[doug-galvanick]

/scratch/duckdb$ go build
/scratch/duckdb$ go mod vendor
/scratch/duckdb$ go build
/usr/local/go/pkg/tool/linux_amd64/link: running g++ failed: exit status 1
/usr/bin/ld: cannot find -lduckdb: No such file or directory
collect2: error: ld returned 1 exit status

/scratch/duckdb$ rm -rf vendor/
/scratch/duckdb$ go build

Sorry for the drive by issue. I just solved it by not using vendor. Might break my Docker build but it works for now. Will follow up if I find a solution.

[doug-galvanick]

Perhaps something like this - https://github.com/pganalyze/pg_query_go#usage-with-go-modules

When integrating this library using Go modules, and using a vendor/ directory, you will need to explicitly copy over some of the C build files, since Go does not copy files in subfolders without .go files whilst vendoring.

[marcboeker]

Thanks for reporting this. I've done some testing to include the deps directory in the vendoring process, but had no success. It seems that go mod vendor only supports Go source files that are imported.

[oleksandr]

perhaps, as a interim solution, the binaries could be placed elsewhere and their location could be provided with an env variable (during the build process), that doesn't conflict with others?

[MathiasGr]

What has worked for me is to add these steps to our CI pipeline, using modvendor to vendor the non-go items.

          # Install and run github.com/goware/modvendor to vendor C dependencies.
          - go install github.com/goware/modvendor@latest
          - modvendor -copy="**/*.a" -v

[james-lawrence]

just add an empty deps.go file to the directory containing the c files and it'll fix itself.