To limit the number of threads, append -jX where X is the number of threads you wish to use. This will perform a parallel build of Chromium using all available threads. Note that clang_base_path will have to be modified to contain the full path to your $CHROMIUM_DIR/llvm_build directory that was created earlier.Ĭlose and save the text file and perform the following to build Chromium: Paste in the following configuration, modified to suit your needs if necessary:Ĭlang_base_path = "$CHROMIUM_DIR/llvm_build" To do this, perform the following:Ī text editor will open. First, the build parameters must be configured with gn. chromium/scripts/build_ffmpeg.py linux ppc64 $ cd $CHROMIUM_DIR/chromium/src/third_party/ffmpeg First though, the ppc64le build files for ffmpeg and libvpx will need to be generated. Now Chromium is almost ready to be built. Note that any errors about already applied patches can be safely ignored. If an error is encountered, you can attempt to rebase the patch manually by following the prompts, or you can create a GitHub issue to notify This will attempt to apply all the patches. $ python3 cpf.py $CHROMIUM_DIR/chromium/src To patch your local copy of the Chromium source, do the following: Included is a script which will apply all the patches to a Chromium source directory. The patches required to build Chromium are maintained here. It is recommended to place the following lines in a file named env.sh that you source, or in your In order to use the tools, they'll need to be in your path. Next is depot_tools, a collection of source code management tools used by Google. $ git checkout 81ee1967d3fcbc829bac1c005c3da59739c88df9 # Latest GN is broken with chromium. This directory will henceforth be referred to as $CHROMIUM_DIR. It is recommended to complete these steps in a new directory reserved for chromium and its dependencies, like ~/chromium_build. Next, you'll need some utilities that most likely aren't available in your distribution's repositories. # apt install git vim cmake python libcups2-dev pkg-config libnss3-dev libssl-dev libglib2.0-dev libgnome-keyring-dev libpango1.0-dev libdbus-1-dev libatk1.0-dev libatk-bridge2.0-dev libgtk-3-dev libkrb5-dev libpulse-dev libxss-dev re2c subversion curl libasound2-dev libpci-dev mesa-common-dev gperf bison nodejs uuid-dev clang-format ninja-build Approximately 1GB per SMT thread seems to be reasonable.īefore beginning, you will need to install Chromium's dependencies from your distribution's package manager.įor Ubuntu, the following should be sufficient: For parallel builds (recommended), theĪmount of RAM required will scale with the number of cores in your machine. To build chromium, you'll need a ppc64le Linux environment with around 70GB of free disk space and at least 8GB of RAM. This page documents how to download and build Chromium for ppc64le. There is an ongoing effort to get the patches upstreamed, but at the moment it is still required to apply some out-of-tree patches to get the browser to build. The base patch set targets CPUs running in Little Endian mode (ppc64le), butĪdditional patches for Big Endian support exist as well. Google's Chromium browser has been ported by the community to run on POWER systems. The old Chromium wiki page is available here: Porting/Chromium_(Old). Īdditional patches required for ppc64 (Big Endian) are available here: Porting/Chromium/BE. Ī source distribution of ungoogled-chromium with the patches incorporated is available here. The repository of all required patches for ppc64le is available here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |