I have to admit, i'm not married to my workflow, as long as I can quickly (< 5 mins) switch libs I'm fine, HDD space and bandwidth are essentially infinite these days my time however is not. That…
I'm not experienced enough with git-lfs to make any worth while contribution to this discussion
I do have a concern this setup will break my current workflow, which is like this:
Blender…
finished final testing, this can land, will land the changed libs on monday
Oh no i'd still happily land this if you update it to the one liner, i just lack the time help you setup your local vscode development environment.
rebuild.cmd does more than just calling…
You're pretty far out of supported territory, sadly we can't support VS code on windows due to it having a thousand nobs to turn and json files tweak to your liking, it's just not something we can…
Honestly for a vscode setup, i'd probably just bootstrap using make full ninja 2022 nobuild builddir ninja_full_2022 and just call ninja in the build dir to build.
running make.bat in a…
While I feel like Make.bat should not be anywhere near a build pipeline or a developers daily workflow (it's designed to bootstrap a build for the most novice of users, I wouldn't not…
I bumped into it a while ago, @deadpin mentioned
it's known. haven't been able to fix it though. the test exposed the issue but it's technically been in blender "forever"
back then.
@brecht / @ideasman42 this seems to be getting close to landing, due to the large nature of this diff, can you guys give a whirl on your respective platforms to make sure nothing broke there?