Also allow Visual Studio 2026 to build from source
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- cmake, cpp
- Domain
- build-system
Research direction
The issue points to setup.py lines 992–993 and provides a Windows build command using CMake, Ninja, CUDA, and Visual Studio 2026. Read that version check and confirm how it affects source builds; compare it with the reported successful build. Done when Visual Studio 2026 is accepted for source builds without breaking existing supported-version checks.
Written by the indexing model from the issue text.
Description
I don't know where the info came from, This is either wrong or outdated:
https://github.com/Niko1221/Strata/blob/6f32ec070f23ced9f50e704d854d775da52591ab/setup.py#L992-L993
I just compiled strata with the following .bat script without any issues:
@echo off
call "C:\Program Files\Microsoft Visual Studio\18\Community\VC\Auxiliary\Build\vcvarsall.bat" x64 >nul
cmake -G Ninja -S . -B ./build ^
-DCMAKE_BUILD_TYPE=Release ^
-DSTRATA_ENABLE_CUDA=ON ^
-DSTRATA_BUILD_TESTS=OFF ^
-DCMAKE_CUDA_ARCHITECTURES=89 ^
-DSTRATA_GGML_DIR=.\third_party\llama.cpp || exit /b 1
cmake --build ./build --target strata -j 8 && exit /b 0
echo (the build stopped - trying it once more)
cmake --build ./build --target strata -j 8 || exit /b 1
As you can see I used Visual Studio 2026 (2026 = version 18)
Cuda version was:
> & "C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v13.3/bin/nvcc.exe" --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2026 NVIDIA Corporation
Built on Tue_Jun__9_14:30:19_Pacific_Daylight_Time_2026
Cuda compilation tools, release 13.3, V13.3.73
Build cuda_13.3.r13.3/compiler.38244171_0
- Dominant language
- C++
- Stars
- 11.6k
- Forks
- 1k
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Niko1221/Strata
-
[Linux] --calibrate combined with --model silently falls through to plain re-setup (setup.py:4958)Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
[Feature]: Log authentication failures with the client source IP (for fail2ban / rate limiting)Open
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
bitcoin-core/gui-qml#1003 ·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
metasequoiaime/msime#7328 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
osam-cologne/archlinux-proaudio#909 ·
Maintainers usually reply within 1 day