-
Notifications
You must be signed in to change notification settings - Fork 15.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: move libcc patches to electron repo #14104
Conversation
I'm going to touch lots of libcc files in electron/libchromiumcontent#647 =/ |
e18c102
to
b460bf2
Compare
Rebased on top of M67 merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Can you please move script/README.md and script/get-patch too?
Also it looks like at least some copied scripts are outdated (e.g. script/lib/git.py
). Probably they have been updated in the libcc repo after this PR was initially created.
Can you please copy them again?
ba6d351
to
1902554
Compare
In the GN build, libchromiumcontent is no longer a distinct library, but merely a container for a set of scripts and patches. Maintaining those patches in a separate repository is tedious and error-prone, so merge them into the main repo. Once this is merged and GN is the default way to build Electron, the libchromiumcontent repository can be archived.
e83c3af
to
5cfdb95
Compare
No Release Notes |
In the GN build, libchromiumcontent is no longer a distinct library, but
merely a container for a set of scripts and patches. Maintaining those
patches in a separate repository is tedious and error-prone, so merge
them into the main repo.
Once this is merged and GN is the default way to build Electron, the
libchromiumcontent repository can be archived.
Depends on #14097.
Notes: no-notes