From 50d28a8ee0371c8da30193e40bd861362ab73ac2 Mon Sep 17 00:00:00 2001 From: Alexander David Frick Date: Thu, 28 Oct 2021 09:27:24 -0500 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index b265e746..407f7e84 100644 --- a/README.md +++ b/README.md @@ -22,7 +22,7 @@ # Building _**The scripts assume the chromium source is at $HOME/chromiums/src/. You may have to sudo chmod +x the scripts to make them executable.**_ -- After initial download of source code, run (from where you cloned this repo) `trunk.sh`. This will update and sync the sources and at the end it will download the PGO profile for chromium. The file will be downloaded to *//chromium/src/chrome/build/pgo_profiles/*.profdata* with the actual file name looking something like 'chrome-linux-main-1632505958-ddbb37bcdfa7dbd7b10cf3a9b6a5bc45e7a958a6.profdata', which should be added to the end of args.gn as per below. +- After initial download of source code, run (from where you cloned this repo) `trunk.sh`. This will update and sync the sources and at the end it will download the PGO profile for chromium. The file will be downloaded to *//chromium/src/chrome/build/pgo_profiles/*.profdata* with the actual file name looking something like 'chrome-linux-main-1632505958-ddbb37bcdfa7dbd7b10cf3a9b6a5bc45e7a958a6.profdata', which should be added to the end of args.gn as per below. - Then (from where you cloned this repo) run `setup.sh`. This will copy all the files and patches to the needed locations. - Run `gn args out/thorium` and the contents of args.gn in this repo should be copy/pasted *--Include your api keys here at the top or leave blank, and edit the last line to point to the actual path and file name file name of '*.profdata'.* - To build, run `autoninja -j8 -C out/thorium chrome chrome_sandbox content_shell -d stats` *The -j# can be changed to limit or increase the number of jobs (generally should be the number of CPU cores on your machine), and the -d stats at the end just shows better verbose stats during compiling. You could also append chromedriver after content_shell to build chromedriver, the selenium compatible browser fuzzing library.*