Feb 8, 2022
RK: (CMSIS-Build - support IAR C/C++ Compiler for ARM) Has anyone reached out to IAR from ST to discuss this project?
JK: I have spoken to IAR. Understand the Tarek making the pull request reached out to IAR. Contact Tarek directly for the IAR contact.
FR: The tool decides what the output is?
DB: Can explicitly set build type and target type
RK: Need to document what you’ve implemented
ED: Suggest to use standard path placeholders with curly braces
Issue #81 “Get rid of project names as much as possible”
JK: Think it’s trying to be quite simplistic.
RK: Proposal is not to include name in a yaml file. (link to Support for unnamed *.yml files). Could have a file starting with a dot and would be hidden.
VG: Depends what we want to promote to the user. Add a UI and use this as metadata
JA: If want users to edit them, don’t want to hide them.
Issue #85 “Handling of Packs”
RK: Take a look and see if there are any problems with it. Believe it should solve ST’s item.
“Open Door to Vendor Specific Data Addon” Issue #83
ED: I need to be able to store the data as it was.
JA: Need to see if we can point to an additional schema file for the vendor specific area.
RK: Need to define the behaviour of the tools in these sections. Have to retain the content.
ED: Would it be better to refer to other files?
RK: Here the suggestion is to allow any key, any value.
RK: Don’t have a good way to integrate CubeMX into a commandline based environment
FR: Proposal is to work slightly differently. At the moment CubeMX does the composition and generates the project files. Perhaps we can split it.