disable cgo when building go code #124572
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
The build settings have been changed so that the executable binary will run regardless of the execution environment.
Changes Made
CGO_ENABLED=0
when compiling custom handler for each OS.Background
In the current document, the custom handler is built with dynamic link.
If you continue using this method, an error will occur when you deploy to Azure Functions, and the function will not run. That's presumably because the dependent C library is not placed in the execution environment. Therefore, I changed it to build the custom handler with static link.
Additional Notes
CGO_ENABLED=0
is described in the official Go documentation below.https://pkg.go.dev/cmd/cgo