About global macro definitions

[tuopu]

Ask the expert for a question.
I want to migrate to a new hardware platform, but the compilation failed. Do you have a more comprehensive migration description.
Is there a default definition independent of hardware that I can add hardware related drivers one by one to realize rapid migration？
I want to put the global macro definition of thread into a header file. Which file is more appropriate, such as "openthread_ftd = 1".
There is also the need to define those global macros when and whether there is a description file. thank you!!

[jwhui]

The build system typically defines this value depending on what it is trying to build.

Some examples:

• openthread/Android.mk

  Line 53 in 237c91b

  -DOPENTHREAD_FTD=1 \

• openthread/BUILD.gn

  Line 46 in 237c91b

  "OPENTHREAD_FTD=1",

• openthread/src/core/ftd.cmake

  Line 32 in 237c91b

  OPENTHREAD_FTD=1

[tuopu]

Hello, expert, thank you for your reply. I'm learning to apply thread to FreeRTOS. When referring to the example, I found that the thread in OT RTOS can't be upgraded to the latest version, and it can't be compiled successfully in Linux. Please ask your latest submitted thread version to apply in FreeRTOS. Do you have any good suggestions?

[tuopu]

One more question，Under the world mechanism of thead, how can we know that the thread is about to arrive, so as to use semaphores and other system functions to inform the task to continue running?

[jwhui]

One more question，Under the world mechanism of thead, how can we know that the thread is about to arrive, so as to use semaphores and other system functions to inform the task to continue running?

Platform drivers handle events (e.g. timer fires, radio packets received, etc.) and those drivers are responsible for scheduling OpenThread execution at the appropriate time depending on the platform's implementation.