Build tweaks for GCCSDK autobuilder, bump to v0.2050b for new libssh2 build #2
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
The version numbering strategy seems pretty peculiar as to why it uses the fourth decimal place, so I unilaterally decided that I'm going to bump the third decimal place and mostly ignore the fourth. I presume the suffix 'b' is for beta and 'r' is for release.
archifishaldev
approved these changes
Jul 28, 2023
dpt
approved these changes
Jul 28, 2023
|
Thanks for this! |
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.
I've made some tweaks to both the GNUmakefile and the GCCSDK build script, which enables building with a new version of libssh2 (in this specific case, 1.10.0) rather than the 13 year old build from 2010. In particular it avoids the need for a hardcoded GCCSDK at /home/riscos. I've also bumped the version number to 0.2050b in anticipation of a release of this version. Hopefully this won't disturb the AMU or JFPaaS builds.
A test build may be found at:
https://www.chiark.greenend.org.uk/~theom/ephemeral/Nettle_0-2050b-1_arm.zip
If this is acceptable I'll also commit the changes to the GCCSDK autobuilder recipe and push out a new build on riscos.info and its PackMan repository.