-
Notifications
You must be signed in to change notification settings - Fork 3k
NRF52: rename the STRINGIFY macro to avoid compiler warnings #7329
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
The changes look good but are they needed? how |
@0xc0170 It may be use in Nordic ble implementation which may also need headers from the OS. |
@0xc0170 Although I don't know why, this changes is really necessary, just like the following:
|
I checked how that common gets in, via some driver includes Looking at the |
I created ARM-software/CMSIS_5#385. From my view, I think we can fix it in RTX as that symbol should not be exposed t here like that for just use in one line (that one is easy to fix). Do not redefine what is already defined (in this case something so generic). |
Update, this should fix the warning: #7364 That Stringify should not get even to the app (we included internal RTX header file). T hus this patch should not be needed then. @pingdan32 please review |
#7364 This PR is a perfect solution, I like it. Thanks. |
@marcuschangarm This is a frieldly review reminder (the changeset is small and straightforward) |
We can close this one. The fix referenced above fixes warnings that were addressed also here. We don't need to edit the 3rd party drivers in this case. Note, I do not like some macros that are exposed from nordic drivers, but that is different task to fix that (@marcuschangarm if you find time to review them, see my #7329 (comment) comment). |
I think @TacoGrandeTX is going to take a look at those warnings in the near future. |
Description
The macro
STRINGIFY
innordic_common.h
conflicts with the macroSTRINGIFY
inrtx_core_cm.h
, which causes the compiler to prompt a large number of warnings when using the IAR to compile the NRF52 platform.This PR avoids these warnings by renaming it to NRF_STRINGIFY.
In addition, it is recommended that it should check if there are too many warnings when main repository merge code. Our current main repository code compiles with a lot of warnings
Pull request type