Is your feature request related to a problem? Please describe. For generic questions use Q&A section in the Discussions forum above.
Hi — I've built a fully native-Windows version of SPAdes 4.3.0-dev (MinGW-w64; no WSL/Docker/VM; all binaries fully static, zero runtime DLLs). All 16 modes run, the official 1K E. coli self-test (spades.py --test) passes, and I've validated assembly end-to-end on real and simulated bacterial genomes (numbers in the repo). Repo: https://github.com/MrMufasii/SPAdes-for-Windows
I wanted to ask directly: is native-Windows support something you'd want upstream, or would you rather it live as a downstream fork?
I ask because the Windows layer is non-trivial and a real maintenance/CI commitment: char-based std::filesystem::path (~90 sites where value_type is wchar_t on Windows), completing the vendored LLVM-Support Unix backend for Windows, and a small POSIX shim (mmap/glob/mkdtemp via CreateFileMapping/FindFirstFile). I'm genuinely happy either way — the fork stands on its own and I'll keep it current — but if you'd want it in mainline I'd gladly work out how to structure it with you.
Full fix-by-fix writeup, including the gdb diagnosis of the trickiest fault: https://github.com/MrMufasii/SPAdes-for-Windows/blob/master/scripts/spades-patch/README.md
Thanks for SPAdes, and for keeping the dev branch open to patches.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
Is your feature request related to a problem? Please describe. For generic questions use Q&A section in the Discussions forum above.
Hi — I've built a fully native-Windows version of SPAdes 4.3.0-dev (MinGW-w64; no WSL/Docker/VM; all binaries fully static, zero runtime DLLs). All 16 modes run, the official 1K E. coli self-test (
spades.py --test) passes, and I've validated assembly end-to-end on real and simulated bacterial genomes (numbers in the repo). Repo: https://github.com/MrMufasii/SPAdes-for-WindowsI wanted to ask directly: is native-Windows support something you'd want upstream, or would you rather it live as a downstream fork?
I ask because the Windows layer is non-trivial and a real maintenance/CI commitment: char-based
std::filesystem::path(~90 sites wherevalue_typeiswchar_ton Windows), completing the vendored LLVM-Support Unix backend for Windows, and a small POSIX shim (mmap/glob/mkdtempviaCreateFileMapping/FindFirstFile). I'm genuinely happy either way — the fork stands on its own and I'll keep it current — but if you'd want it in mainline I'd gladly work out how to structure it with you.Full fix-by-fix writeup, including the gdb diagnosis of the trickiest fault: https://github.com/MrMufasii/SPAdes-for-Windows/blob/master/scripts/spades-patch/README.md
Thanks for SPAdes, and for keeping the dev branch open to patches.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response