| Age | Commit message (Collapse) | Author |
|---|
|
Problem: MS-Windows makefiles are inconsistently named.
Solution: Use consistent names. (Ken Takata, closes #11088)
|
|
Problem: MS-Windows: various warnings.
Solution: Set the charset to utf-8. Add _WIN32_WINNT and _USING_V110_SDK71_.
(Ken Takata, closes #5625)
|
|
Problem: Compiler warning with VS2019.
Solution: Specify different offset for "AMD64". (closes #4235)
|
|
Problem: No support for Windows on ARM64.
Solution: Add ARM64 support (Leendert van Doorn)
|
|
Problem: Using old compiler on MS-Windows.
Solution: Switch default build on MS-Windows to use MSVC 2015. (Ken Takata)
|
|
Problem: win32.mak no longer included in Windows SDK.
Solution: Do not include win32.mak. (Ken Takata)
|
|
Problem: Cannot build with new MSVC version VS2017.
Solution: Change the compiler arguments. (Leonardo Manera, closes #1731,
closes #1747)
|
|
Problem: Code for MS-Windows is complicated because of the exceptions for
old systems.
Solution: Drop support for MS-Windows older than Windows XP. (Ken Takata)
|
|
Problem: Visual studio tools are noisy.
Solution: Suppress startup info. (Mike Williams)
|
|
Problem: Can't build GvimExt with SDK 7.1.
Solution: Support using setenv.bat instead of vcvars32.bat. (Ken Takata)
|
|
Problem: Building GvimExt with VS2015 may fail.
Solution: Adjust the makefile. (Mike Williams)
|
|
Problem: Cannot build GvimExt.
Solution: Set APPVER to 5.0. (KF Leong)
|
|
Problem: Can't always find Win32.mak when building GvimExt.
Solution: Use same mechanism as in Make_mvc.mak. (Cade Foster)
|
|
|
|
|
|
|
|
|
