I was attempting to call xEventGroupSetBitsFromISR in an embedded application with out trace capability. This function is commented out if trace facility is disabled. It seems like the trace function call inside the function could just be disabled if tracing isn’t supported. Would I be OK to just use this by modifying around the trace requirement? Or is there something else I might not be aware of?
I have partially resolved this issue. Everything builds correctly when buildling in the target with trace turned off. However I was cross-compiling in Windows and had trace turned on, and that was causing the issues above. I have turned trace off for both the Windows build and the embedded build and I’m not seeing any build problems.
What I found was that if trace is turned off, the header file redefines the xEventGroupSetBitsFromISR to just call xTimerPendFunctionCallFromISR with an additional needed function callback argument. So if trace is turned off, it really doesn’t expect that function to need to be compiled in. But for some reason when building it in Windows with trace turned on, it was still needing a xEventGroupSetBitsFromISR function implementation and wasn’t able to find it, which brought me to the above conditional compile checking.