Repository navigation
Fix issue 3574: Specified version for jasper due to upstream build error - #3591
Merged
christophe-murphy merged 1 commit intoAug 30, 2024
Merged
christophe-murphy merged 1 commit into
christophe-murphy merged 1 commit into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
…tream build error
christophe-murphy
approved these changes
Aug 30, 2024
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.
Jasper, a dependency of freeimage, caused a vcpkg build error when using the vcpkg cmake toolchain to build arrayfire. This was caused due to a build error upstream with Jasper. This sets a specific version for jasper which does not have that error.
Description
Fixes: #3574
Changes to Users
Checklist