@feodor2Can you 7z up and send me your C:\DEV folder similar to how I've done this with VS2019? https://archive.org/details/funny-windows-development-kit
I can't use my FWDK itself with Mypal68 as it complains about some error that I've forgotten. So I went to use EWDK, but you seem to have modified EWDK as using the ISO you linked and unpacking it into the folder results in it complaining about the Win 10 SDK being too old. I've used MSVC14 folder from EWDK and Windows Kits folder from FWDK to compile and that's worked fine from Firefox 68+, however using it to build latest Mypal68 gives me these errors.
Not sure tbh, Mypal68 uses the LLVM 9 that you can download and that could be used for reference. For 68, on top of that you need a llvm-config.exe, which you can get from compiling Rust. For 78 and later, llvm-dlltool.exe is also required to be added.
Also the listed minimum Clang up to 140 at least is still 9, so maybe I will just continue on and fix what comes. 102 was actually kinda painless, and 115 hasn't been too bad so far. 91 made me think it would be horrible because I had to bisect a bunch.
No? I've just been working on it over the months and years. I started at 122, and basically have had a release for every major version.
idk if it's possible, I think it will be a lot and very hard going by Mypal68 changes on top of extrapolating to like 140 or so if I were to try it. A lot of the reason I wanted to try this was to have a build system to build older releases that can no longer be bootstrapped. With this, I was able to build 91, and disable WebRender and have Cairo on a (relatively) recent version. https://github.com/Eclipse-Community/r3dfox/issues/32#issuecomment-4262918711