This issue doesn't seem to be entirely resolved. I have two variants Debug vs. Release, which use two different build directories ("build/Debug" and "build/Release") and therefore caches. Even if I set "Skip over the configure process if cache is present", configure seems to always rerun upon switching between the variants. Is there currently a way to prevent this, or does this require a fix?
I can confirm that in other circumstances this fix/option seems to do the right thing: If I simply stop the build and restart (without switching variants) I see the following in the output and configure is indeed skipped:
The extension determined that a configuration is needed at this moment but we are skipping because the setting cmake.skipConfigureWhenCachePresent is ON. Make sure the CMake cache is in sync with the latest configuration changes.
Originally posted by Wojciech Jarosz (@wkjarosz) in #984 (comment)
This issue doesn't seem to be entirely resolved. I have two variants Debug vs. Release, which use two different build directories ("build/Debug" and "build/Release") and therefore caches. Even if I set "Skip over the configure process if cache is present", configure seems to always rerun upon switching between the variants. Is there currently a way to prevent this, or does this require a fix?
I can confirm that in other circumstances this fix/option seems to do the right thing: If I simply stop the build and restart (without switching variants) I see the following in the output and configure is indeed skipped:
Originally posted by Wojciech Jarosz (@wkjarosz) in #984 (comment)