downgrading compiler version with Arm Tools Environment Manager not working

[andbararm]

Type: Bug Report

Describe the bug

• OS and Version: tested on Windows 11
• VS Code Version: 1.96.2
• Extension Version: 1.46.0
• Arm Tools Environment Manager: 1.10.0

The expected procedure (given in Arm Tools Environment Manager Settings "Reactivate On Config Change" is enabled) to change used Arm Compiler version is to change the vcpkg-configuration.json file, save it and do a "Rebuild Solution". However this only works when upgrading the compiler, like from 6.22 to 6.23. This did not work for downgrading the compiler like from 6.23 to 6.22. As a workaround one can execute from the Command Palette the command "Developer: Reload Window" and then doing a "Rebuild Solution".

Steps to reproduce the behavior:

1. Go to 'vcpkg-configuration.json'
2. Downgrade the compiler version from like 6.23 to 6.22 and save the file.
3. Do a "Rebuild Solution"
4. Problem: in compile_commands.json still the version 6.23 is in use.

Expected behavior

The compile_commands.json should show that the version 6.22 is in use.

[jkrech]

This is most likely an issue with the CMSIS-Toolbox cbuild setup command.

[brondani]

When reactivating vcpkg the new environment variables are set but the old ones are not unset as it would be expected.
For this reason downgrading the compiler is not reflected in the build: both environment variables are set so the lower version is overruled by the higher version.

This happens with vcpkg package management program version 2023-11-16-4c1df40a3c5c5e18de299a99e9accb03c2a82e1e which is currently shipped within the Arm Tools Environment Manager extension.
It does not happen with newer vcpkg versions, it was probably fixed in microsoft/vcpkg#36025

The vcpkg upgrade was already requested in ARM-software/vscode-environment-manager#8

[ReinhardKeil]

I believe a workaround is to restart VSCode

[JonatanAntoni]

I believe a workaround is to restart VSCode

Deactivating the environment explicitly and reactivate it cleanly does the job. One doesn't need to restart VSCode as a whole.

[JonatanAntoni]

Filed Arm-Debug/vscode-environment-manager#175. We can't do anything about it in CMSIS Solution extension.