cryptography: Enable ability for a standalone build #27
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 is to break a cyclic build dependency between clientlibraries and libprovision, if we move to a vault implementation of libprovision. In existing builds, it will still build as part of clientlibraries. This just gives the option to invoke a build directly in Source/cryptography without moving cryptography in a separate repo.
Current cyclic dependency if we move to the vault powered libprovision: