Add a simple Windows command-line build script #6674
Conversation
Batch file that offers a single command line and sensible defaults to: initialize the primary Visual Studio build environment, handle directory creation/cleaning, run cmake, launch msbuild, etc.
|
Thank you indeed. I have merged into master. Where did you draw you inspiration from? I was not aware this is doable with Windows batch at all. Would you please extend the script so it will allow defining the destdir with a relative path, such as the following?
Thank you. |
I was just annoyed that PR #6667 was wrong entirely because I hadn't wanted to hassle with a full deps-up rebuild. So, I just mashed up and polished off some of my old batch files, to make it easy to do command line rebuilds in the future. And I figured I'd share in case anyone else found it useful. Anyway, Windows batch is an ugly language, and PowerShell will probably make it unnecessary in another few years. But it's still the most universal scripting language on Windows, and something I just know from doing Windows dev and security since WinNT 4 in the mid '90s.
Yeah, it should be easy to have |
|
How does it install slicer? Or how should it be started? |
3 participants
Batch file that offers a single command line and sensible defaults to: initialize the primary Visual Studio build environment, handle directory creation/cleaning, run cmake, launch msbuild, etc.
It should work on any running version of Windows, as I believe all command and shell options used are supported from at least Vista onward.
Usage examples:
build_win -d "c:\src\PrusaSlicer-deps"build_win -s allbuild_win