Repository navigation
Pin SWIG 4.4.1 across package builds - #239
Merged
Merged
Conversation
This was referenced Oct 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Pin SWIG 4.4.1 across Linux, macOS, and Windows package builds so each platform generates the same C# API surface.
shared/swig.lockContext
This addresses the ABI consistency concern raised in OSGeo/gdal#15079. SWIG versions below 4.2 do not support the C#
cs:defaultargsfeature used by that bindings overhaul, which could otherwise give the same NuGet package version a different API surface on Linux.Tests
swig -versionreports 4.4.1ci/Dockerfile.vcpkg)