2 ms·
> so I have no idea why you'd want to do this on Windows. If you're trying to write portable software, that's the easiest way to validate compilation for Linux
by viraptor 9y ago
> so I have no idea why you'd want to do this on Windows.
If you're trying to write portable software, that's the easiest way to validate compilation for Linux without: a) using an external CI, or b) running a full VM in parallel.
- boterock 9y agobut you can also install clang 5 in windows... I don't think it would be that different. I don't use it too much, but I have it for clang-format
- mbel 9y agoWell, since we are speaking about clang there is always cross compilation option: "clang -target x86_64-linux" (note, that it supports all targets that your current build of clang has enabled). But probably the real option (c) that you are missing here is the fabulously named "Windows Subsystem for Linux".
- viraptor 9y agoRe crosscompilation: Sure, if you want to prepare an environment which has all the dependencies, then that is a way you can take. I always found it harder than using the target system directly. And in the end if you're running any tests after compilation, you still need the target system for that. Re WSL: If the app you're working on works on WSL, great. It's not an option for many projects though.
- icebraining 9y agoRunning containers on Windows requires a full VM in parallel. Docker just hides it.
- viraptor 9y agoTechnically, yes. But by full VM, I mean a parallel desktop/server system with permanent storage that you have to maintain in different ways to a temporary container. Same technologies, different user experience. Docker hides it by providing a nice layer on top.