#675 If the “Compiler’s installation directory” setting contains variables, an incorrect warning is produced at startup

[New Pagodi]

This is a similar issue to #674 but about a different problem. If I have defined the compiler variable
VCVERSION=14.13.26128 and set the the compiler’s installation directory area on the toolchain executables page of the compiler settings dialog to

C:\Program Files\Microsoft Visual Studio 2017\VC\Tools\MSVC\$(VCVERSION)\bin\Hostx64\x64

codeblocks can correctly find and invoke the compiler, resource compiler and linker. (Actually, the resource compiler is in a folder specified on the additional paths page, but I don’t think that’s important for this issue.)

However when codeblocks launches, it pops up a warning that it can't find the compiler in the executable search path. I think this is because the variable is not expanded in the check done at start up, because if you use C:\Program Files\Microsoft Visual Studio 2017\VC\Tools\MSVC\14.13.26128\bin\Hostx64\x64 for the compiler’s installation directory, there is no warning at startup.

[Teodor Petrov]

Can you copy-paste the exact message C::B is showing or can you show me a screen shot of the dialog that pops up?
I need to this in order to find the place where the error happens.

[New Pagodi]

I can't select the text, but here is a screen shot: