4 ms·
> I've tried to get a build system going a few times in MS land, but I'm too used to the relative simplicity of gcc and make files and find I have little patien
by pjc50 6y ago
> I've tried to get a build system going a few times in MS land, but I'm too used to the relative simplicity of gcc and make files and find I have little patience for what feels like massive overkill for building simple command line tools.
Embrace the target: use Visual Studio (community edition)
You can still write in vim if you want, you just tab over and hit F5 when you want to run.
MSBuild has a steep learning curve, but I've recently managed to climb it using https://docs.microsoft.com/en-us/visualstudio/msbuild/msbuild-concepts?view=vs-2019 https://docs.microsoft.com/en-us/visualstudio/msbuild/msbuil...
Coming from make, a make target is a msbuild "item". Variables become properties. Build steps are "tasks" - generally you use the builtin ones.
- greggyb 6y agoVsVim is pretty good vim emulation for Visual Studio.
- jcelerier 6y ago> You can still write in vim if you want, you just tab over and hit F5 when you want to run. or just use cmake with nmake or ninja generator if you are that hellbent on using cl.exe
- pjc50 6y agoI'd like to ask the opposite question of this thread: why is everyone so hellbent on not using the Microsoft tooling?
- GoblinSlayer 6y agoPortability is more realistic with portable tooling.
- Iwan-Zotow 6y agoPortability it is really different... I'm using LLVM on Windows - native binaries, calls to clang and clang++ with the same options as gcc. So LLVM+cmake+ninja works reasnable well for medium sized project
- jcelerier 6y agocmake is much more sane imho. And works everywhere. I have nightmares of msbuild.