[go: nahoru, domu]
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.

Sign up for GitHub

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

Jump to bottom

chromium tarball is much too big: split source? #763

Open
rwmacleod opened this issue Oct 15, 2023 · 1 comment
Open

chromium tarball is much too big: split source? #763

rwmacleod opened this issue Oct 15, 2023 · 1 comment

Comments

@rwmacleod
Copy link
Contributor
rwmacleod commented Oct 15, 2023 •
edited
Loading

@nrpt-m mentioned that with upstream adding Rust in chromium 117, the tarball is ~3 GB.
Even before this, chromium-116.0.5845.187.tar.xz is 1.5 GB and 13 GB unpacked.
It seemed hard to believe that all of that data would be required to build chromium.
Using ncdu, the top level directories that are > 100 MiB are:

    9.7 GiB [##########] /third_party                                                                                                                                                         
  822.8 MiB [          ] /chrome
  420.8 MiB [          ] /components
  288.4 MiB [          ] /buildtools 
  199.6 MiB [          ] /tools
  126.0 MiB [          ] /ios
  110.9 MiB [          ] /net
  104.3 MiB [          ] /ui
  101.0 MiB [          ] /ash

and the largest third-party componets are:

    1.6 GiB [##########] /llvm  
    1.5 GiB [######### ] /angle
    1.0 GiB [######    ] /swiftshader
  649.2 MiB [###       ] /dawn                                                                                                                                                                
  454.5 MiB [##        ] /devtools-frontend
  373.9 MiB [##        ] /catapult

Is it possible to use llvm and rust from YP/OE and does anyone think that it would be a good idea to look at other large directories and remove them or split them into a seperate tarball if not needed. Does anyone object to such a change assuming that it's not too painful to implement and maintain?
@rakuco
Copy link
Collaborator
rakuco commented Oct 17, 2023

The tarball publishing process upstream already creates a tarball called "chromium-lite" which removes some directories, but this list is not very up-to-date and actively maintained.

As a first step one could see if this tarball is considerably smaller than the one we use and whether one can actually build Chromium from it.

As for using LLVM and Rust from YP/OE and the rest of the suggestion: do you mean creating a tarball of our own?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rakuco @rwmacleod