So I've been going through the setup guide for Windows and I was hitting the wall because it was failing the .bat scripts. So it had some paths hardcoded for some reason and let's say if I install my visual studio into a different disk from the system then %PROGRAMFILES% will lead to disk C where no visual studio exists.
If it is of any value to the community I can push pull request that instead uses industry standard vswhere script that is installed with every modern visual studio instalation. It allows to query visual studio installed (if multiple are installed) and select the one you are interested in, then get all the needed paths from it.
So I've been going through the setup guide for Windows and I was hitting the wall because it was failing the .bat scripts. So it had some paths hardcoded for some reason and let's say if I install my visual studio into a different disk from the system then %PROGRAMFILES% will lead to disk C where no visual studio exists.
If it is of any value to the community I can push pull request that instead uses industry standard vswhere script that is installed with every modern visual studio instalation. It allows to query visual studio installed (if multiple are installed) and select the one you are interested in, then get all the needed paths from it.