- This topic has 3 replies, 2 voices, and was last updated 2 weeks, 6 days ago by
.
-
Posts
-
When you open a project with a missing toolchain (com.visualgdb.arm-eabi) it will prompt you to either retrieve the missing toolchain or use the current version installed.
This works as expected to update the toolchain of the first configuration. It does not however update the toolchain of other configurations of the same project.
I can open the vgdbcmake file and see that the first VisualGDBConfiguration in the file updates. All the other configurations use the old the dependency.
This would be fine if when you switch configurations it prompted you to update them, but instead it errors during cmake configuration and the only way to fix it is to manually edit the vgdbcmake file to update the dependencies.
System.Exception: Missing toolchain: com.visualgdb.arm-eabi. Please install it via VisualGDB Package Manager.
at u04.h4(IDELevelProjectInfoForBuilding a)
at u04.f3(lh3 a)
at u04.a2(k b, Int32 a)Hi,
No problem, this should be fairly easy to fix. Just to double-check, are you using the same toolchain in all the configurations?
In this instance yes, all the configurations use the same toolchain. I could see cases where you have configurations that use entirely different toolchains, but I can’t imagine an instance where you would want different versions of the same toolchain. If there is some use for this it probably wouldn’t be a good idea always update them together.
I think the best solution would be just to show the same resolution window that initially appears loading a project when you switch to a configuration with a missing dependency.
Hi,
Switching configurations in VS is somewhat tricky. It involves a lot of work on different levels of Visual Studio itself, so adding extra steps there could break some of them.
So, we updated the checking logic to make a list of all toolchains referenced by all configurations/platforms, and if any of them is missing, you can substitute them individually. So, different configurations were using different toolchains, they will still be separate after the update.
We have currently added it to CodeVROOM (stand-alone port of VisualGDB). You can try this build: CodeVROOM-0.8.0.354.exe; it doesn’t need installation, you can just run the executable, open an existing .vgdbcmake project, and it will show the new substitution GUI if any missing toolchains are discovered. We will add this to the next VisualGDB update as well.
- You must be logged in to reply to this topic.