On Fri, 17 Jul 2026 at 00:23, Daniel Sahlberg <[email protected]> wrote:
> Den ons 15 juli 2026 kl 14:58 skrev Ivan Zhakov <[email protected]>: > ... > >> >> Also I think we should drop support vcxproj support in the long term. >> > > Agree. I would support a decision to announce it as deprecated and planned > for removal in a subsequent release. The reason for deprecating and not > just removing it is that it is currently a functional build system and it > might disturb downstream users if we just remove it. > > Can we reach consensus on a decision already before the release of 1.15? > > +1 for announcing vcxproj as deprecated and planned for removal in a subsequent release. Some more datapoints in support of this: 1. The vcxproj-based build is conceptually different from CMake and autoconf. In practice, we are maintaining two similar build systems plus the entirely separate one in form of vcxproj. 2. Supporting vcxproj makes some improvements around the CMake build noticeably harder to implement. For example, running tests via win-tests.py would currently require two side-by-side/conditional implementations. 3. Removing vcxproj support on trunk would let us finish remaining work for CMake to reach parity with autoconf. Which would then allow us to declare CMake the default in 1.16. -- Ivan Zhakov
