GUACAMOLE-2236: Change build against FreeRDP development versions fro…#641
Merged
mike-jumper merged 1 commit intoapache:staging/1.6.1from Mar 1, 2026
Merged
Conversation
…m error to warning.
mike-jumper
approved these changes
Mar 1, 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
2 participants
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.
As discussed in #640, the most recent release of FreeRDP 2.x left the
-devcomponent in the version string, causing our builds against FreeRDP 2.x to break unless the --enable-allow-freerdp-snapshots flag is specified. The FreeRDP team has stated that they will fix this at some point, but, until then, this PR changes theAC_MSG_ERRORpreviously sent by the configure script intoAC_MSG_WARN, warning the operator of the danger of building against FreeRDP snapshots, but allowing the build process to continue.