[RFC] boards: Introduce CONFIG_BOARD_SUPPORT_REMOTE_ENDPOINT #39790
Conversation
carlocaione
requested review from
MaureenHelm,
dleach02,
galak,
ioannisg and
mmahadevan108
as code owners
The IPC samples are currently hardcoding the local and remote target boards in the sample CMakeLists file. Instead of relying on the sample to define the target board names introduce a new CONFIG_BOARD_SUPPORT_REMOTE_ENDPOINT symbol to signal the build system that the remote endpoint target name can be set by the board cmake file in the REMOTE_BOARD variable to be used by samples at compile time. Signed-off-by: Carlo Caione <[email protected]>
|
@carlocaione Thanks a lot for this. At dev-review meeting, the multi image issue came up once more when #37872 was discussed. This has led to an RFC which tries to address multi image support once again here: #40555 I've included a commit that also takes a baby step related to IPC samples, just for prototyping. I think this PR has some good direction together with #40555, so let's keep this open and consider this along side the other PR. |
|
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
3 participants
The IPC samples are currently hardcoding the local and remote target board names in the sample CMakeLists file.
Instead of relying on the sample to define the target board names introduce a new
CONFIG_BOARD_SUPPORT_REMOTE_ENDPOINTsymbol to signal the build system that the remote endpoint target name can be set by the board cmake file in theREMOTE_BOARDvariable to be used by samples at compile time.This was requested by @tejlmand in #39470 (comment). Probably it's not the definitive solution or the one that he was expecting but it's a good starting point for discussion at least :)