-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Adding in ability to support a library for freertos_config and a custom port #571
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
…om freertos_kernel_port (FreeRTOS#558)
Codecov ReportBase: 94.30% // Head: 94.30% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## main #571 +/- ##
=======================================
Coverage 94.30% 94.30%
=======================================
Files 6 6
Lines 2370 2370
Branches 579 579
=======================================
Hits 2235 2235
Misses 85 85
Partials 50 50
Flags with carried forward coverage won't be shown. Click here to find out more. Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
|
Thanks for your comments . I've responded with all of them, and have allowed the FREERTOS_CONFIG_FILE_DIRECTORY to be backwards compatible - but with a warning to update when used. If you like I can separate the ports each into separate CMakeLists.txt as well which would help simplify and limit the case statements in the port directory to just one (which one it selects). |
|
Note - I have a follow-on PR for fixing the compiler warnings here: phelter#1 will change target to master once this PR is completed. |
|
@paulbartell @aggarg - Any chance we can move the needle on this PR? I've performed all of the changes you've requested. And am waiting for this one to be merged to start the next one. Thanks |
…efault PORT selection for native POSIX and MINGW platforms.
|
@paulbartell @aggarg - Ping again. Need a maintainer to approve running the workflows for this PR and would appreciate some time to identify any further issues that need to be resolved. Thanks |
paulbartell
left a comment
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.
IMO, defining and linking a target similar to freertos_config should be left to the user.
@paulbartell - You've requested a change. I am unclear as to what that change is that will get approval for this PR. With no changes:
For Linking - with this PR - if Are you asking NOT to link If this is the case - then the user will have NO indication that there is missing configuration required while performing the If you are still requiring a change here, can you please provide a proposal of how to provide a standardized way a I am unclear as to what must be done next to move this PR along. Thanks |
… it from a FREERTOS_CONFIG_FILE_DIRECTORY.
|
@AniruddhaKanhere , @aggarg or @archigup - Ping again. Would appreciate a review of the changes requested by @paulbartell |
|
@AniruddhaKanhere , @aggarg or @archigup - Ping once again. Just so you know this has been opened closing in on almost 2 months now. |
|
@phelter, apologies for the delay, I was out of office and was travelling. Thank you for your patience and your efforts in creating this PR. Thanks, |
7c2e999
Description
DEPRECATE: CMake:
FREERTOS_CONFIG_FILE_DIRECTORYconfiguration and replace it with expected libraryfreertos_configRationale - some configuration settings can now be added to the
freertos_configtarget eg:Added support for
FREERTOS_PORT=A_CUSTOM_PORT- this allows the inclusion of a port as a library as well that can be linked to the FreeRTOS-Kernel appropriately.Assorted fixes:
Compiller->CompilerTest Steps
Setup a local cmake project and use the following project file to include FreeRTOS-Kernel