3 ms·
There is something fundamentally wrong with Windows or Visual Studio that it requires ugly solutions.
by uecker 7mo ago
There is something fundamentally wrong with Windows or Visual Studio that it requires ugly solutions.
- delta_p_delta_x 7mo agoWindows and Visual Studio solutions are perfectly fine. MSBuild is a declarative build syntax in XML, it's not very different from a makefile.
- uecker 7mo agoXML is already terrible. But the main problem seems to be that they created something similar but incompatible to make.
- flohofwoe 7mo agoOk, then just cl.exe instead of gcc or clang. Completely different set of command line options from gcc and clang, but that's fine. C/C++ build tooling needs to be able to deal with different toolchains. The diversity of C/C++ toolchains is a strength, not a weakness :) One nice feature of MSVC is that you can describe the linker dependencies in the source files (via #pragma comment(lib, ...)), this enables building fairly complex single-file tools trivially without a build system like this: cl mytool.c ...without having to specify system dependencies like kernel32 etc... on the cmdline.
- account42 7mo ago> Completely different set of command line options from gcc and clang, but that's fine. Clang does have clang-cl with similar command-line options.
- account42 7mo agoAt least you can use the compiler/linker without them.