Gn cc32 xxsdk 2 10 00 04 #1
Open
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 allows compatibility with header files of wolfssl 3.10.4
…se of exception thrown on CC3220 h/w)
…ect and libXively makefiles. And some notes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
We updated wolfSSL in libXively to 3.10.7-stable because of our desire to use libXiv and libIOTC together in same (ccs) project. This entailed a few file additions/changes to the wolfSSL ccs project in libXively. Found that libIOTC requires quite a few more configuration flags - most notably HAVE_ECC. A lot of time has been expended trying to understand and nail down the WolfSSL config for libIOTC - for now, am stopping here with the addition of HAVE_ECC related configuration flags. My xively-client branch is restricting these modifiection to the CC3220 bsp at this time as I am unsure of the implications of making these changes in mt-tls-wolfssl.mk.
First pull request ever so please pardon and advise (or ignore) if I am doing something outside of expected workflow.