Note: All issues have been closed without waiting for people’s review and validation feedback. Please raise a new issue / bug with reference to the original issue in case the implementation does not meet expectations
Raising awareness that the Open-CMSIS-Pack recommended landing page is: https://github.com/Open-CMSIS-Pack This is where the purpose of the different repositories are listed and should help for people to find their way.
Eric (ST) provided feedback that a colleague found it difficult to navigate to the cproject input format specification. It was suggested to treat the yaml input format similar to the CMSIS-Pack specification. Reinhard (Arm) responded that he would prefer to keep it this way, as there is currently only one implementation (csolution)
Demo of VSCode using CMSIS-Toolbox by Joachim (Arm)
The README.md in this repository describes the steps to setup Visual Studio Code, clone the repository and build the solution relying on vcpkg-configuration.json file to install and activate thre pre-requisites: CMSIS-Toolbox (ctools), cmake, ninja and GCC arm-none-eabi toolchain.
Demonstrated new features:
compiler registration: set environment variable <compiler>_TOOLCHAIN_<major>_<minor>_<patch> to point to bin directory of the toolchain installation
e.g. Win: set AC6_TOOLCHAIN_6_19_0=c:\Keil_v5\ARM\ARMCLANG\bin
display registered toolchains:
csolution list toolchains -v
override compiler selection from the command line: GCC is set as default in .cdefault.yml
this is either the directory where the cproject.yml or clayer.yml files are located, depending on where the components associated with a generator are listed. Note: components of a single generator must not be distributed across cproject and clayer files.
Next meeting is on 2023-03-7 @ 16:00 CET
Note that there will not be a Open-CMSIS-Pack Technical Project meeting the week after next (2023-03-14) due to Embedded World 2023.