Build: Updated CMAKE_C_FLAGS for IAR #375
No reviewers
Labels
No labels
api-spec
bug
CLA requested
CLA valid
compliance
DO NOT MERGE
duplicate
enhancement
feature branch
good first issue
HEADER FORMATTING ISSUE
help wanted
Information
invalid
Jira status: AWAITING REVIEW
Jira status: CLOSED
Jira status: DONE
Jira status: IN PROGRESS
Jira status: IN REVIEW
Jira status: OPEN
Jira status: REOPENED
Jira status: RESOLVED
mirrored
mirror internally
needs: backports
needs: ci
needs: design review
needs: preceding PR
needs: review
needs: work
notabug
open for community contribution
Product Backlog
question
ready for merge
security
stale
type: bug
type: enhancement
type: question
web pages
wontfix
writing
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-ARMmbed/mbed-crypto!375
Loading…
Reference in a new issue
No description provided.
Delete branch "development"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Updated the IAR specific CMAKE_C_FLAGS settings in CMakeLists.txt to
allow building TF-M (Trusted Firmware) with mbed-crypto as a subproject.
Signed-off-by: TTornblom thomas.tornblom@iar.com
What are the failing CI tests? I have no access to the details of the failed tests.
All of the mbed-os tests using K64F with GCC_ARM and IAR are failing. The build is stopped pretty soon, so this is probably not the only error that will be encountered:
Please build one of the mbedtls mbed-os examples (like hashing, or benchmark), by running:
mbed compile -m K64F -t GCC_ARMormbed compile -m K64F -t IARin the respective directory to get full results.I don't see that this is connected to my update in any way.
This appears to have broken with the update to the latest mbed-crypto in mbed-os and should be addressed there, not with my fix.
Appears that attest_crypto_keys.c, which is part of mbed-os, is using deprecated constants, which is why compilation fails. I would be highly surprised if this compiles with any toolchain.
@gilles-peskine-arm Please review
Everything passed in the CI except some known issues independent from this PR.