-
Notifications
You must be signed in to change notification settings - Fork 923
Setting CGO_ENABLED=0 for next release
#4037
Unanswered
kyleconroy
asked this question in
Feature Requests & Ideas
-
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/sqlcand the new build will be
CGO_ENABLED=0 GOOS={os} GOARCH={arch} go build -ldflags="-s -w" ./cmd/sqlcBefore 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
-
🎉 3
Replies: 1 comment
-
Hi, fairly new SQLC user here. What are the differences, pros, and cons between the two? I'd assume that CGO_ENABLED=0 will lead to more portable binary.
Beta Was this translation helpful? Give feedback.
All reactions
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment