* [qt5-webengine] Manually add nodejs to the path (microsoft#23574)
The build process requires nodejs to be in PATH when webengine is
built, and will build only the pdf-plugin if it's not (see #23574)
* [qt5-webengine] Workaround MSVC2022 Internal Compiler Error
(microsoft#23574)
Add a patch based on
https://codereview.qt-project.org/c/qt/qtwebengine-chromium/+/407582
which was merged into upstream. We can't take the upstream patch
directly, because the patch was committed to the chromium
(sub)repository which is a subdirectory in the release zip file, i.e.
I had to modify the pathnames for the patch to apply
* [qt5-webengine] Update diagnostics (microsoft#23574)
I've spotted the linker using 16GB singlehandedly on the release
(opposed to "debug") packaging, and emory consumption was almost
permanently over 32GB while compiling, though peak memory
consumption can be reduced by setting up low values for
VCPKG_MAX_CONCURRENY
Also, reword the build-prefix-too-long message
* [qt5-webengine] Attempt enabling windows ci baselines (microsoft#23574)
* [qt5-webengine] Regenerate version registries (microsoft#23574)
* Also remove out of date comments from ci.baseline.txt referring to deleted lines.
* Revert "Also remove out of date comments from ci.baseline.txt referring to deleted lines."
This reverts commit 7a4d84643102231bf8e60f2340db970c8775a607.
* [qt5-webengine] Re-add webengine blacklisting to ci.baseline (microsoft#23574)
Co-authored-by: Billy Robert O'Neal III <bion@microsoft.com>
63f1d5b4d0