Allow compiling without SSL #96
Open
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
Note that we use the same cmake variable as in rabbitmq-c so both libraries are always compiled in the same way.
|
Note that there will be a conflict with #98 but I will be happy to resolve it once either of the PRs is merged. |
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.
This PR adds the ability to compile without SSL.
rabbitmq-calready has that ability, but until now compiling it without SSL lead to errors becauseamqpcppalways expected it to be compiled with SSL.Since we now use the same cmake variable as in
rabbitmq-cboth libraries are always compiled in the same way.An exception is raised in case the user requests a SSL connection from a library that is compiled without SSL support.