2026 Ready

.github/workflows/build_all.yml

@@ -26,7 +26,7 @@ on:
      - 'version.inc'
      - ".github/workflows/build_*.yml"
      - 'build_linux.sh'
-     - 'build_release_vs2022.bat'
+     - 'build_release_vs202X.bat'
      - 'build_release_macos.sh'
      - 'scripts/flatpak/**'
 

.github/workflows/build_deps.yml

@@ -69,8 +69,8 @@ jobs:
         working-directory: ${{ github.workspace }}
         run: |
             choco install strawberryperl
-            .\build_release_vs2022.bat deps
-            .\build_release_vs2022.bat pack
+            .\build_release_vs202X.bat deps
+            .\build_release_vs202X.bat pack
             cd ${{ github.workspace }}/deps/build
 
       - name: Build on Mac ${{ inputs.arch }}

.github/workflows/build_orca.yml

@@ -233,7 +233,7 @@ jobs:
         env:
           WindowsSdkDir: 'C:\Program Files (x86)\Windows Kits\10\'
           WindowsSDKVersion: '10.0.26100.0\'
-        run: .\build_release_vs2022.bat slicer
+        run: .\build_release_vs202X.bat slicer
 
       - name: Create installer Win
         if: inputs.os == 'windows-latest'

AGENTS.md

@@ -8,7 +8,7 @@ Use out-of-source builds:
 - `cmake -S . -B build -DCMAKE_BUILD_TYPE=Release` configures dependencies and generates build files.
 - `cmake --build build --target OrcaSlicer --config Release` compiles the app; add `--parallel` to speed up.
 - `cmake --build build --target tests` then `ctest --test-dir build --output-on-failure` runs automated suites.
-Platform helpers such as `build_linux.sh`, `build_release_macos.sh`, and `build_release_vs2022.bat` wrap the same flow with toolchain flags. Use `build_release_macos.sh -sx` when reproducing macOS build issues, and `scripts/DockerBuild.sh` for reproducible container builds.
+Platform helpers such as `build_linux.sh`, `build_release_macos.sh`, and `build_release_vs202X.bat` wrap the same flow with toolchain flags. Use `build_release_macos.sh -sx` when reproducing macOS build issues, and `scripts/DockerBuild.sh` for reproducible container builds.
 
 ## Coding Style & Naming Conventions
 `.clang-format` enforces 4-space indents, a 140-column limit, aligned initializers, and brace wrapping for classes and functions. Run `clang-format -i <file>` before committing; the CMake `clang-format` target is available when LLVM tools are on your PATH. Prefer `CamelCase` for classes, `snake_case` for functions and locals, and `SCREAMING_CASE` for constants, matching conventions in `src/`. Keep headers self-contained and align include order with the IWYU pragmas.

CLAUDE.md

@@ -11,16 +11,16 @@ OrcaSlicer is an open-source 3D slicer application forked from Bambu Studio, bui
 ### Building on Windows
 ```bash
 # Build everything
-build_release_vs2022.bat
+build_release_vs202X.bat
 
 # Build with debug symbols
-build_release_vs2022.bat debug
+build_release_vs202X.bat debug
 
 # Build only dependencies
-build_release_vs2022.bat deps
+build_release_vs202X.bat deps
 
 # Build only slicer (after deps are built)
-build_release_vs2022.bat slicer
+build_release_vs202X.bat slicer
 
 
 ```

doc/developer-reference/How-to-build.md

@@ -28,15 +28,15 @@ Whether you're a contributor or just want a custom build, this guide will help y
 
 ## Windows 64-bit
 
-How to building with Visual Studio 2022 on Windows 64-bit.
+How to building with Visual Studio on Windows 64-bit.
 
 ### Windows Tools Required
 
-- [Visual Studio 2022](https://visualstudio.microsoft.com/vs/) or Visual Studio 2019
+- [Visual Studio 2022](https://visualstudio.microsoft.com/vs/), 2026 or 2019
   ```shell
   winget install --id=Microsoft.VisualStudio.2022.Professional -e
   ```
-- [CMake](https://cmake.org/) — **⚠️ version 3.31.x is mandatory**
+- [CMake](https://cmake.org/)
   ```shell
   winget install --id=Kitware.CMake -e
   ```
@@ -81,14 +81,18 @@ How to building with Visual Studio 2022 on Windows 64-bit.
      git lfs pull
      ```
 2. Open the appropriate command prompt:
-   - Visual Studio 2019:
+   - Visual Studio 2026:
      ```MD
-     x64 Native Tools Command Prompt for VS 2019
+     x64 Native Tools Command Prompt for VS
      ```
    - Visual Studio 2022:
      ```MD
      x64 Native Tools Command Prompt for VS 2022
      ```
+   - Visual Studio 2019:
+     ```MD
+     x64 Native Tools Command Prompt for VS 2019
+     ```
    1. Navigate to correct drive (if needed), e.g.:
       ```shell
       N:
@@ -98,16 +102,16 @@ How to building with Visual Studio 2022 on Windows 64-bit.
       cd N:\Repos\OrcaSlicer
       ```
    3. Run the build script:
-      - Visual Studio 2019:  
+      - Visual Studio 2026 or 2022:
         ```shell
-        build_release.bat
+        build_release_vs202X.bat
         ```
-      - Visual Studio 2022:  
+      - Visual Studio 2019:
         ```shell
-        build_release_vs2022.bat
+        build_release_vs2019.bat
         ```
 
-![vs2022cmd](https://github.com/SoftFever/OrcaSlicer/blob/main/doc/images/develop/vs2022cmd.png?raw=true)
+![vs202Xcmd](https://github.com/SoftFever/OrcaSlicer/blob/main/doc/images/develop/vs202Xcmd.png?raw=true)
 
 > [!NOTE]
 > The build process will take a long time depending on your system but even with high-end hardware it can take up to 40 minutes.
@@ -115,13 +119,13 @@ How to building with Visual Studio 2022 on Windows 64-bit.
 > [!TIP]
 > If you encounter issues, you can try to uninstall ZLIB from your Vcpkg library.
 
-3. If successful, you will find the Visual Studio solution file in:
+1. If successful, you will find the Visual Studio solution file in:
    ```shell
    build\OrcaSlicer.sln
    ```
-4. Open the solution in Visual Studio, set the build configuration to `Release` and run the `Local Windows Debugger`.  
-   ![compile_vs2022_local_debugger](https://github.com/SoftFever/OrcaSlicer/blob/main/doc/images/develop/compile_vs2022_local_debugger.png?raw=true)
-5. Your resulting executable will be located in:
+2. Open the solution in Visual Studio, set the build configuration to `Release` and run the `Local Windows Debugger`.  
+   ![compile_vs202X_local_debugger](https://github.com/SoftFever/OrcaSlicer/blob/main/doc/images/develop/compile_vs202X_local_debugger.png?raw=true)
+3. Your resulting executable will be located in:
    ```shell
    \build\src\Release\orca-slicer.exe
    ```