build: Build all YIO components from GitHub source #57
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
All YIO components are now built from their GitHub repository sources, and no longer downloaded as binary releases. Not only is this more "Buildroot style", but also allows to adapt to new Qt versions more quickly or use other build environments.
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.
All YIO components are now built from their GitHub repository sources, and no longer downloaded as binary releases.
Version numbers are still the same and usually directly relate to a GitHub release, which has the same number as Git tag. Furthermore, one can now also use commit hashes for a specific development build.
Not only is this more "Buildroot style", but also allows to adapt to new Qt versions more quickly or use other build environments.
Using binary YIO releases are no longer supported.
This supports #3 in using newer Qt versions. It resolves the chicken-egg issue and no longer depends on GitHub binary releases.