Visual Studio 2026

[UCyborg]

OK, but technically we're not changing Mozilla Build, at least essentials like Python binaries and the like, just putting compilation additional tool there because it was probably the easiest thing to do.

BTW, I notice these warnings:

Code: Select all

22:11.88 cl : Command line warning D9002 : ignoring unknown option '-msse4.1'

Did someone erroneously specify an option that doesn't exist somewhere?

[UCyborg]

Does anyone happen to know if binaries compiled with v145 toolset are supposed to break on Windows 8.1 too? Assuming the source code doesn't unconditionally call Win7 incompatible APIs. I don't have that v145 compiled Pale Moon anymore...have few other DLLs compiled with v145 toolset though and they load. Though perhaps it will be faster if I just install Win7 myself to confirm whether 7 breaks / 8.1 works.

[UCyborg]

I can open the DLL in OllyDbg, but actually using it in application throws DllNotFoundException. Bummer.

[UCyborg]

Actually, the DLL failed when runtime DLLs from Microsoft.VC145.CRT were there in the folder. It worked when omitted or copies from Microsoft.VC143.CRT were there. I don't remember if I tried this with PM built with VS 2026...but I usually religiously clear those DLLs from ALL and ANY program I install.

It's shared code that doesn't belong there, period.

Now the question is, when would VC145 versions be "needed"? When certain C++ features are used? That video I watched recently said MS' compiler is (or was) the leading one when it comes to implementing C++ features.