Setting CGO_ENABLED=0
for v1.30
#4037
Unanswered
kyleconroy
asked this question in
Feature Requests & Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Earlier this year we switched to using a version of the PostgreSQL parser that didn't require cgo. For v1.30, I'm planning on releasing binaries that are build slightly differently. The old build command was
go build -ldflags="-s -w -extldflags \"-static\"" ./cmd/sqlc
and the new build will be
CGO_ENABLED=0 GOOS={os} GOARCH={arch} go build -ldflags="-s -w" ./cmd/sqlc
Before officially changing the build, I wanted to gather input from the community, specifically if this would cause any issues with your current setup.
Beta Was this translation helpful? Give feedback.
All reactions