How to compile this source code

[longyixiao]

No description provided.

[win32ss]

It should be the same as the regular process of compiling the Chromium source code, but instead of pulling from the chromium repository, pull from this one. As this one is now out of date, you may want to pull from the tag for the last commit from upstream that I've applied here.

I also made a modification to webrtc which is in a different git repo, so you would have to pull from my variant of it as well, which I will upload promptly.

[longyixiao]

ok，Thank you

[longyixiao]

Error reported according to chrome compilation method

[win32ss]

Please provide the details of this error.

I have also added several other repositories for "third-party" Chromium components in recent weeks. They are in the form of multi-part zips because GitHub does not seem to be able to handle a git push from a repository hosted off of GitHub (indeed, these are Google-hosted repositories without GitHub mirrors) then cloned locally.

Once unzipped they will be in the form of git repositories. If they don't work well with the rest of a newer Chromium repository, then you may simply obtain the details of the most recent commits and apply them to the latest version of these third-party components.

[win32ss]

Did you run gclient sync (or more specifically, gclient sync -m to avoid overwriting my customizations to the third party repos)?

I will probably end up supplying Supermium and its components in git-compatible patch form so it can be easier to build using the standard Chromium build process and also because it's the preferred way to modify Chromium for Electron.

[longyixiao]

Not running gclient sync and gclient sync - m
After obtaining the Superpremium code, run gclient runbooks directly

[win32ss]

gclient sync is required to obtain all the third-party repos I believe.

[longyixiao]

Thank you, I compiled it，But Win7 did not run successfully
gclient sync updated the compilation tool chain error in the runbooks step. To ensure that runbooks pass, I set DEPOT_ TOOLS_ UPDATE, DEPOT_ TOOLS_ WIN_ TOOLCHAIN environment variable, the final compiled execution file cannot run on Win7 64 bit. My compilation environment is vs2019 for Win10, and I have installed Win10.0.22621.1778 sdk

[win32ss]

Just gclient sync or gclient sync -m? As stated above, gclient sync will tend to overwrite the third-party repos instead of merging them. I found it strange at first as well when I started seeing missing functions in Dependency Walker like GetDpiForMonitor, which I had thought I had removed earlier.

So I would check for any missing functions in Dependency Walker. Some are not important, but some of those are "delay-loaded functions that are called in all cases" and would cause problems.

[longyixiao]

I only ran the gclient sync command on my end
Did not run the gclient sync - m command
How to update and merge into the third-party repository you modified

[longyixiao]

Did I choose the wrong compilation environment

[win32ss]

It's the right environment, A Windows build is a Windows build. But gclient sync -m would merge the upstream commits with my commits.... which are only in the other Supermium repositories I have made (boringssl/v8/webrtc). Although I will eventually change everything from full repositories to patches to make it easier for other users (and also to make it possible to build as Electron).

[adeii]

"gclient sync -M" or "gclient sync --merge" helps to start compiling on
Win 8.1 with Windows SKD 10.22 and VS 2022 17.6 community.
Just edit " date_val = 1691765800 #int(args.timestamp) " in src/base/write_build_date_header.py