git.blender.org got yanked from underneeth me, and i didn't keep any numbers, but the maintainance done last weekend has improved things on the new server, the old server ~is~ was still 4x…
I gave you the greenlight for a single VS related ignore, you submitted a patch with a whole bunch of other stuff in it, which I had to ask a second reviewer time for, and you're now not sure…
VS looks fine, i'd like to get @JacquesLucke opinion on the vscode additions though
initital pass/lowhanging fruit only, haven't been able to build just yet.
Took me a bit to realize what this did, 'L'? what's 'L'? only when you scroll down you realize it's a flag, I'd prefer LIBDIR_FLAG and just add the - here as well so it's even clearer that it is indeed a flag.
you can't hardcode 2022 here, we still support 2019 and you can't link libraries build with 2022 with older compilers, compat only works in one direction there. build in 2019 -> linked with 2022 is fine.. the otherway around is not.
not super obvious in the online diff viewer, but this produces
That's problematic, i need to be able to rebuild LTS releases for 2 years without getting all kinds of unrelated updates, the old system grabbed the packages once, and for the important ones like compiler versions they were pinned versions so there's no surprise GCC 10->11 update with all kinds of new adventures in it.
This gives me the Heebie-jeebies, i'd rather see this as a patch for gmp or put the script straight up in build_files\build_environment\patches\
If a single additional ignore makes your life a little easier, go for it, unsure why this needed a TODO ticket which are normally reserved for module members. You could just have asked on chat.
List of available updates as of today (automatically gathered, could have mistakes)