Add Go version check before building OCI library to prevent build failures #47
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.
Problem
The build fails with cryptic errors when an older Go version (< 1.21) is used, because the
oci-go/go.modfile requires features that were introduced in Go 1.21:The error occurs during the build phase, making it difficult to diagnose. Users with older Go installations would see the build fail partway through with confusing error messages.
Solution
Added a Go version check in
common/CMakeLists.txtthat runs before attempting to build the OCI library. The check:go versionto get the installed Go versiontoolchaindirective support)Implementation Details
The version check handles various Go version formats (
1.21,1.21.0,1.22rc1, etc.) and includes proper error handling for:go versioncommand executionWhen Go < 1.21 is detected, users now see a clear message:
The build then continues successfully without OCI support, rather than failing with cryptic errors.
Testing
Impact
This change ensures that:
Original prompt
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.