WOLFMQTT_EXAMPLE_CERT allowing static or extern cert assignment #354
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.
Related to #352, this PR introduces the
WOLFMQTT_EXAMPLE_CERT
to allow theCMakeLists.txt
in an Espressif Managed Component project to build the AWS example using the certs defined in examples/aws/awsiot.c and used in the examples/mqttexample.c source.GitHub Workflow Update Included
edit: Thank you @bandi13 for the .github/workflows/ubuntu-check.yml update included here that helped identify the occasional workflow network failure, as well as the workflow updates in #355.
Background
Without this change, included files outside of the project directory like this:
... fail to properly build:
The PR is an alternative to my current method of copying those files to the local project directory. Although the copy works, it is one more point of maintenance when the example certs expire.
Usage
Define
WOLFMQTT_EXTERN_CERT
either inuser_settings.h
, or in the case of Managed Component examples, thiscmake
line is added to the main projectCMakeLists.txt
:See also the published wolfSSL Managed Component.