-
Notifications
You must be signed in to change notification settings - Fork 3k
Fix missing linkage of mbed-mbedtls-cryptocell310 to mbed-mbedtls #14435
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
feature object libraries branch has this fixed for all drivers almost.
Jenkins CI Test : ❌ FAILEDBuild Number: 1 | 🔒 Jenkins CI Job | 🌐 Logs & ArtifactsCLICK for Detailed Summary
|
The failure is related. to my understanding: mbedtls is not enabled in CMake, build fails. This will work for examples that link to mbedtls, but not for apps that do not need mbedtls. We looked at this briefly but haven't found a solution. It's known issue. A target can add additional libraries, in this case tls as the driver requires it, but should it be linked always? An app can choose what to link to, but what about a target. |
@0xc0170 In other Mbed TLS drivers we simply add the driver code as part of mbed-mbedtls. I can do that. |
2321e8e
to
29474cf
Compare
29474cf
to
2228aa7
Compare
@0xc0170 Done |
The CMake target mbed-mbedtls-cryptocell310 was not linked by default, resulting in a compilation error on targets that use Mbed TLS: fatal error: mbedtls_device.h: No such file or directory Other Mbed TLS drivers simply add themselve to mbed-mbedtls, so this commits does the alignment to fix the build error. Note: the driver and the core Mbed TLS have mutual dependency, so they need to be one CMake target.
2228aa7
to
4c6f886
Compare
CI started |
Jenkins CI Test : ❌ FAILEDBuild Number: 2 | 🔒 Jenkins CI Job | 🌐 Logs & ArtifactsCLICK for Detailed Summary
|
CI restarted |
Jenkins CI Test : ✔️ SUCCESSBuild Number: 3 | 🔒 Jenkins CI Job | 🌐 Logs & ArtifactsCLICK for Detailed Summary
|
Summary of changes
The CMake target mbed-mbedtls-cryptocell310 was not linked by default, resulting in a compilation error on targets that use
Mbed TLS:
Other Mbed TLS drivers simply add themselve to mbed-mbedtls, so this commits does the alignment to fix the build error.
Note: the driver and the core Mbed TLS have mutual dependency, so they need to be one CMake target.
Impact of changes
Migration actions required
Documentation
None.
Pull request type
Test results
Reviewers
@0xc0170 @hugueskamba @rajkan01