Currently Stack is using MinGW32/MinGW64 under Windows to cope with C/C++/Fortran dependencies. Stack + Nix is a great tandem that could be turned into very easy to deploy system on most major operating systems. That way Haskell will become even more popular language. Currently Nix support Linux and Mac OS only.
What you think over the idea to use MinGW tooling in combination with Nix for building C/C++ dependencies under Windows?
It's probably not what you want, but I used to use nix for cross-compilation Linux->MinGW – to do CI on Windows SW without actually needing any Windows. Some packages needed fixing, but most problems could be resolved by finding patches on the internet (pushed those to the official nixpkgs repo).
I heard of standard nix used on i686-cygwin, not too long ago, but it's certainly not among the "top-tier" platforms.
Great! I mean in general to be officially supported.
IMHO "official support" is mainly about getting enough people interested so they manage to keep it working well. Some basic cross-compiled binaries are produced by the build farm already: http://hydra.nixos.org/jobset/nixpkgs/cross-trunk#tabs-jobs
So it is possible (theoretically) Stack to run under Windows (with MinGW) and do use Nix package system for building dependencies under Windows for Windows?
@varosi with WSL, I think it should be possible. This is something I'm interested in as well.
@midipix may be another option.
But... it may be better if we can go NATIVE, i.e., no dependency, no framework.
@domenkozar I do not think that using WSL is "under Windows".
Has anyone ever been able to build Nix itself through MinGW? I would be interested in seeing if anything works. Multi-user stuff is pretty reliant on POSIX things but the basic Nix commands are pretty straightforward C++. I'm sure the filesystem would struggle though.
I think MinGW/MSYS2 bash per se can be considered native.
Most helpful comment
@domenkozar I do not think that using WSL is "under Windows".