Build mbedcrypto from other directory than mbedcrypto root dir. #2
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.
Made some changes in CMake to make the mbedcrypto library also 'buildable' from a different directory than the mbedcrypto root directory. This is useful when a CMake project, say
Project A
, uses the library.Project A
has the mbedcrypto repo as a submodule in the directoryProjectA/dep/mbedcrypto
.The developer of
Project A
can add the library simply by adding this code toProjectA/CMakeLists.txt
:From that point the library is linked to
Project A
.The library can still be tested with
mbedcrypto_tests
. After callingcmake
andmake
from the (unix) Terminal, the developer can test the library by executing:If this pull request will be approved, I'm also planning to add a wiki page to the repo that describes how to link the mbedcrypto library to your own project as developer.