4 ms·
One option would be to use Visual Studio Build Tools (https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=BuildTools&rel=16 https://visu
by Sindisil 6y ago
One option would be to use Visual Studio Build Tools (https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=BuildTools&rel=16 https://visualstudio.microsoft.com/thank-you-downloading-vis...).
You could stick with makefiles by using nmake. It's not nearly as full featured as gnu make, and both cmd and PowerShell are much different (and less powerful in the case of cmd) to bash. Still and all, I've made it work quite well in the past for the Windows build of a library I was responsible for in my former day job.
Another option would be to use cmake as your build tool and let it generate ninja, msbuild, or nmake scripts for you. It's not nearly as bad as it was in the past (nor as bad as some might lead to to believe). Worth a try, anyway.
- auxym 6y agoThere's also the option of going in .NET/C# land with the cross platform dotnet SDK (previously known as .NET Core): https://dotnet.microsoft.com/download https://dotnet.microsoft.com/download It's a CLI based full blown SDK including compiler, package manager and build tools, and it's cross platform.
- pjc50 6y agoI love C# and am very impressed with dotnet, but it still has a few limitations - to make it portable you have to ship the runtime with the application, it's not a ""real"" AOT compiled binary. And like all "portable" environments you quickly realize that some of the key native APIs aren't in the portable subset.