Manually Install Swig 4.0.2 from Github on CI #705
Merged
Conversation
This file contains 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
ptheywood
force-pushed
the
ci-swig-manual-install
branch
from
a60084d
to
e615201
Compare
ptheywood
force-pushed
the
ci-swig-manual-install
branch
from
e615201
to
4e22d9f
Compare
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.
Closes #697
Swig occasionally fails to download from sourceforge on CI jobs, but github based Swig releases require
yacc, which we don't want to add as an additional dependency to regular builds.By installing
bisonfromapt(foryacc) and building Swig 4.0.2 from GitHub on CI prior to CMake, this should hopefully make CI more robust.This is not viable for Windows CI workflows, not neccesary for lint/docs work flows, and not neccessary for manylinux workflows where the manylinux container used already contains very recent swig.