While I can’t think of any examples that don’t simply involve macro definitions, that change could turn out to be overrestrictive if in the future we stumble upon other driver arguments that can show up there.
Based on the discussion we had on the most recent Embedded Sync Call, this is the modification proposed:
Multilib flags declarations
Each flag value may specify a list of macro defines that will be passed on to the compilation if that flag value is enabled.
As an example, a custom flag declaration for multithreading that works for newlib:
Flags:
- Name: multithreaded
Values:
- Name: no-multithreaded
MacroDefines: [__SINGLE_THREAD__]
- Name: multithreaded
Default: no-multithreaded
Each item <str>
in the MacroDefines
list is passed on to the compilation in the -D<str>
format. This format also supports macro definitions in the form <name>=<value>
.
MacroDefines
is an optional field.
The Pull Requests already reflect these most recent changes.
Hi all,
I hope you had a good holiday break.
Can you please have a look at the proposal and the Pull Requests? We’d like to make progress soon.