You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a question about how the :defines: section may be composed.
Let say I need to set a lot of MACROs, say MACRO_A, MACRO_B... for a given file 'UT_Flash_Ext_Proxy', so that the mock it uses gets generated accordingly. The manual way of doing it would be to exhaustively set these MACROs in the :defines: section.
However, this list of MACROs is out of my control and may change along time or for different product versions. In fact, this list of MACROs can be regenerated at any given point of time, using an existing shell script.
To cope with this variability, while still using the Ceedling flow, I intend to invoke this script during the pre-mock step, something like:
and then somehow "load" the script-generated file from within the :defines: section.
Before going further in that direction, I would like to know if the :defines: section can afford some compilation symbols to be loaded from an external file or not ? And if yes, what is the command to do so ?
(Note that I do not consider patching the :defines: section of the .yml file before launching Ceedling, as to keep a seamless and automated flow)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello all,
I have a question about how the
:defines:section may be composed.Let say I need to set a lot of MACROs, say MACRO_A, MACRO_B... for a given file 'UT_Flash_Ext_Proxy', so that the mock it uses gets generated accordingly. The manual way of doing it would be to exhaustively set these MACROs in the
:defines:section.However, this list of MACROs is out of my control and may change along time or for different product versions. In fact, this list of MACROs can be regenerated at any given point of time, using an existing shell script.
To cope with this variability, while still using the Ceedling flow, I intend to invoke this script during the pre-mock step, something like:
and then somehow "load" the script-generated file from within the
:defines:section.Before going further in that direction, I would like to know if the
:defines:section can afford some compilation symbols to be loaded from an external file or not ? And if yes, what is the command to do so ?(Note that I do not consider patching the
:defines:section of the .yml file before launching Ceedling, as to keep a seamless and automated flow)Thank you for your help
Beta Was this translation helpful? Give feedback.
All reactions