Document Visual Studio 2022 and 2026 Windows builds#1458
Open
bmehta001 wants to merge 1 commit into
Open
Conversation
Clarify the VS2019/VS2022/VS2026 command-line build entry points, avoid legacy .NET Framework 4.0 projects in VS2022+ wrappers, and make solution-level :Build targets work through RunMsBuild. Files changed: - docs/cpp-start-windows.md - build-all.bat - build-all-v143.bat - build-all-v145.bat - tools/RunMsBuild.bat - tools/setup-buildtools.cmd - tools/vcvars.cmd - tools/.vsconfig.vs2022 - tools/.vsconfig.vs2026 - Solutions/before.targets Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
bmehta001
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Addresses the VS2022/VS2026 Windows build documentation gap from #1260 and keeps related Windows build-script fixes in one focused PR.
build-all-v145.batfor VS2026/v145 and teachvcvars.cmdto find VS2026 installs.:Buildtargets intools/RunMsBuild.batso project builds work consistently.setup-buildtools.cmdto use the existing.vsconfig.vs*naming scheme and add VS2022/VS2026 configs.Validation
git diff --checktools\RunMsBuild.bat x64 Release sqlite:Buildwith VS2026/v145tools\RunMsBuild.bat x64 Release "sqlite:Build,zlib:Rebuild"with VS2026/v145.vsconfig.vs2026.Fixes #1260
Notes: