- User Since
- Aug 21 2018, 4:06 PM (97 w, 6 d)
Jun 5 2020
I have installed Build Tools for VS2019 and the installation is at
C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools
I found this string inside HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\1eb19443 which honestly doesn't seem the proper key to extract this value but anyway.
Sep 23 2019
Sep 22 2019
Sep 17 2019
Minimum cmake version is bumped to 3.1.0.
Sep 14 2019
Some wrong tabs and spaces are fixed.
Sep 13 2019
In the top level CMakelists.txt I added build system support for C++14 which was necessary for the qOverload macro.
Sep 12 2019
Aug 23 2019
This functionality would be great.
Jul 11 2019
Jun 10 2019
brauch is referring to this
echo Define which compiler for VS2017 to use. Possible architectures are:
Jan 29 2019
Jan 28 2019
Upload the minimum diff.
Jan 1 2019
Oct 25 2018
Oct 12 2018
I hate tο be a naysayer here, but shouldn't we not assume that VS2017 is installed in C:\Program Files (x86) so that we don't hardcode it's path? I remember my self installing VS once in another drive, because C:\ was tiny and full.
This batch file seems very clean and simple, I like it. Unfortunately I can't help reviewing this patch as I no longer have access to Windows machines and I don't a dual-boot system :(
Oct 9 2018
Our script now initializes the environment correctly (at least for VS2017) even if the user doesn't run it from Developers Command Prompt. It reads Registry to find the path under which VS2017 is installed (I fear that I read the wrong variable from the Registry).
Can a windows user with VS installed, give me the content of HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\SxS\VS7?
People with Visual Studio other than Community Edition, please consider trying out these changes. If a typo or a bug exists, it should be found early.
- The script (sadly) uses hardcoded paths for vcvarsall.bat, instead of needing VS150COMNTOOLS. This way it can be found and executed, without the need of Developer's Command Prompt.
Oct 8 2018
@kfunk As I already have mentioned, clicking the script (finding it in Start menu) doesn't initialize correctly the environment. It has to be run from within Developer Command Prompt or the complete path of MSCV binaries (for the wanted target) has to be in %PATH%.
Oct 6 2018
Not sure about x64 part. What if user wants x32 project? Or that is arch of the toolchain itself?