Skip to content
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

Merged
merged 3 commits into from
Sep 14, 2018
Merged

build: move libcc patches to electron repo #14104

merged 3 commits into from
Sep 14, 2018

Conversation

nornagon
Copy link
Member

@nornagon nornagon commented Aug 15, 2018

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.

  • PR description included and stakeholders cc'd
  • PR title follows semantic commit guidelines

Notes: no-notes

@nornagon nornagon requested a review from a team August 15, 2018 05:30
@alexeykuzmin
Copy link
Contributor

I'm going to touch lots of libcc files in electron/libchromiumcontent#647 =/

@alexeykuzmin alexeykuzmin self-assigned this Aug 30, 2018
@nornagon nornagon force-pushed the merge-libcc branch 2 times, most recently from e18c102 to b460bf2 Compare September 12, 2018 00:05
@nornagon
Copy link
Member Author

Rebased on top of M67 merge.

Copy link
Contributor

@alexeykuzmin alexeykuzmin left a 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?

DEPS Outdated Show resolved Hide resolved
@alexeykuzmin
Copy link
Contributor

alexeykuzmin commented Sep 12, 2018

@jkleinsc Do we still use sccache binaries from the libcc repo?
UPD I created #14575.

@alexeykuzmin alexeykuzmin removed their assignment Sep 12, 2018
@alexeykuzmin
Copy link
Contributor

alexeykuzmin commented Sep 12, 2018

@nornagon
This PR should be rebased on the latest master to get changes from the now merged #14575.

@nornagon nornagon force-pushed the merge-libcc branch 3 times, most recently from ba6d351 to 1902554 Compare September 13, 2018 18:42
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.
@nornagon nornagon changed the title [wip] build: move libcc patches to electron repo build: move libcc patches to electron repo Sep 13, 2018
@nornagon nornagon merged commit 76c5f5c into master Sep 14, 2018
@release-clerk
Copy link

release-clerk bot commented Sep 14, 2018

No Release Notes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants