I'm working on a project with several Git submodules, some of which contain an IAR project (.ewp file). When the submodules are loaded after opening VS Code, the IAR Build extension opens the CMSIS package manager for these projects and closes it again shortly after. This can happen multiple times in a row. It seems to happen on other occasions as well, but the reason is not clear to me. One can prevent this behavior by adding the .ewp files to the files.exclude setting of VS code. I have this problem with IAR 9.32.1, IAR Build extension 1.20.3 and VS Code 1.75.1.
The IAR Build extensions should not open the CMSIS Package Manager automatically. It also would be nice if the IAR Build extensions would excluded the projects listed in .gitignore, so one can use patterns like the follwing, which currently are not possible in both the files.exclude and the iar-build.projectsToExclude settings
# Exclude all projects except the application
/**/*.ewp
!/**/application.ewp
I'm working on a project with several Git submodules, some of which contain an IAR project (.ewp file). When the submodules are loaded after opening VS Code, the IAR Build extension opens the CMSIS package manager for these projects and closes it again shortly after. This can happen multiple times in a row. It seems to happen on other occasions as well, but the reason is not clear to me. One can prevent this behavior by adding the .ewp files to the files.exclude setting of VS code. I have this problem with IAR 9.32.1, IAR Build extension 1.20.3 and VS Code 1.75.1.
The IAR Build extensions should not open the CMSIS Package Manager automatically. It also would be nice if the IAR Build extensions would excluded the projects listed in .gitignore, so one can use patterns like the follwing, which currently are not possible in both the files.exclude and the iar-build.projectsToExclude settings