...
\uD83D\uDC65 Participants
(Can be filled from Zoom meeting report)Evgueni Driouk
Sourabh
Frédéric Ruellé
Joachim Krech
Reinhard Keil
Erik Mållberg
Maxime DORTEL
Samuel Hultgren
David Jurajda
Mike Susen
Matthew Gordon
Duc Nguyen
Daniel Brondani
Graham Hammond
Holt Sun
Kyle Dando
Slides
|
Meeting Notes
(
General guidance:
record all issue numbers discussed as ‘#nnn’ to allow searching on a particular issue across meeting records
record any decisions and actions
Any other note taking is optional
)
Meeting Recording
(Zoom recording uploaded via Files & Images)Summary of changes in CMSIS-Toolbox 1.6.0
New Proposals presented:
#843 specify
define
as YAML key:value pair - replace ‘=' with ':’Access Sequences ‘clean-up’: see https://github.com/Open-CMSIS-Pack/devtools/blob/main/tools/projmgr/docs/Manual/YML-Input-Format.md#access-sequences
Simplify output taking back some flexibility causing confusion rather than adding value
https://github.com/Open-CMSIS-Pack/devtools/blob/main/tools/projmgr/docs/Manual/YML-Input-Format.md#access-sequencesIntroducing the notion of
context-set
○ #823 needs review after deciding on context-setcontext-set is the combination of contexts with different build-types to be used in a development/debugging/testing scenario where all Debug or all Test build-types is not desired or not practical
This has implications for the command line, the cbuild-idx.yml as well as the access sequences referenceing artifacts from another context
Request for feedback:
is cbuild-idx.yml the right place to store the context-set information? What are alternatives
what other gaps need to be closed (i.e. debug, flash)
ST/Samuel to come up with a flow diagram of using cbuild.yml files as ‘lockfile’ to review cli and IDE flows.
Updates and Review requests for:
#855, #834, #841, #840, #833, #832, #819, #820, #826, #825, #822
Meeting Recording
...