 |
Committed in svn rev 7600 (points 1, 2, 4, 5). UPDATE: fixed bug in svn rev 7613. Now VC redistributable installation is a separate step. When it runs, it first checks whether 32-bit and 64-bit packages should be installed (depending on OS and registry keys). If none are needed (e.g. packages are already present), then the whole step is silently skipped (although some GUI messages remain). If it is clear that vcredist has to be installed, then a message box is shown, waiting for user confirmation. It explains that redist packages will be installed, probably requiring admin rights. After user clicks OK, the redist packages are run sequentally (each of them triggers UAC dialog, unless tdm_update was started under admin). After installers terminate, we check once again if installing VC redist-s is still necessary --- it can be so only if installer failed. In such case we display a warning (another message box) which says that VC redist failed to install and user has to install it manually. After the check, installation process continues as usual. On the frontend side, I have updated messages/titles/progress bar for the new step in Windows GUI installer. I did not change console updater because: 1. On Linux it will silently go through the VC redist installation step, so messages needed. 2. On Windows it will install VC redist if necessary. And in such case it will display various messages anyway. Also, console updater is rarely used on Windows, and if it is, then it cannot be run under user anyway, so vcredist should install without any issues. P.S. Point 3 is not needed. Point 0 (update registry keys for MSVC2017/2.07 runtime) is still TODO. |
|
|
Committed new change in svn rev 7614. Now tdm_update checks registry keys for MSVC2017. So it won't work correctly with TDM 2.06 anymore (which used MSVC2013). On the other hand, now it should work correctly for the future TDM 2.07 =) |
|
|
I resolve this issue, but we should pay close attention to VCRedist installation during 2.07 beta. |
- Anonymous
