Add bcrypt support for UWP development #61
Merged
Conversation
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
This fixes boostorg#47
Contributor
Author
|
@Lastique do you want me to rebase this? There are no conflicts so it should be fine, but I can rebase it to kick off a new set of tests. Let me know. This is the last thing holding me off from submitting Boost.Random changes. |
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.
The older windows crypto methods are not available in some UWP partitions (like
WINAPI_PARTITION_PHONE_APP). To support those, specifically in random number generation methods, bcrypt support is added.I have built against this using local changes in Boost.Random and it works for the phone partition.