Chromium for 64 and 32-bit Windows - Thursday, 12 December 2019

Chromium 79.0.3945.79 (Official Build)
Revision 29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916}
OS Windows

No Sync - WebRTC - Widevine - All Codecs - ThinLTO - Ungoogled

• SDK 10.0.18362.1 (Visual Studio 2019 16.4.0)
• Linux cross-compiled (default compiler)
• No Vulkan

Standard build of Eloston's ungoogled-chromium. All patches applied (safe-browsing removed, not possible to include due to its tight integration with ungoogled.)

ungoogled-chromium-79.0.3945.79-1_windows.7z (64-bit)
SHA1 82AFE790C92D30AEF98D889C51DCE4E14242ADD6

Ungoogled-Chromium-79.0.3945.79-Win32.7z (32-bit)
SHA1 4E978D49D8CEAECFE77CDDE86AB709417EFCA9B6

Safe browser patch not applied:

ungoogled-chromium-79.0.3945.79-1_SB_windows.7z (64-bit)
SHA1 55552B22862E6E55FDFCC99416BC04DDBE647475

====================================================

=== PATCH FILE ===

Patch applied to git 29f75ce3f42b007bd80361b0dfcfee3a13ff90b8 79.0.3945.79 before pruning

79.0.3945.79.diff.7z
SHA1 95F8A3ACCE92F55C0A035206BE262E3362277D82

NB:

core/ungoogled-chromium/disable-domain-reliability.patch

In order to cross-compile had to change:

components/domain_reliability/BUILD.gn

output_file = "$target_gen_dir/baked_in_configs.cc"
@@ -39,13 +19,21 @@ action("bake_in_configs") {

The JSON file list is too long for the command line on Windows, so put

them in a response file.

• response_file_contents = rebase_path(inputs, root_build_dir)
• args = [
• "--file-list",
• "{{response_file_name}}",
• "--output",
• rebase_path(output_file, root_build_dir),
• ]

• if (is_win) { <<<< CHANGED TO (!is_win) >>>>>>