.
├── build.sh # Main script to build chrome
├── chr # This dir will be attached as volume to the docker container
│ ├── buildchrome.sh # This script runs in container and automates build
│ ├── chromium
│ │ └── src # Chromium source code
│ ├── configs # Configs for building various versions of chrome
│ │ ├── 56-gcc4.9
│ │ ├── 56-gcc5.4
│ │ └── ....
│ ├── sysroots # Must contain sysroots for builds
│ │ │── baikal-rootfs-chromedeps # must be downloaded manualy
│ │ └── yocto-fp64-sysroot
│ │ └── .....
│ └── toolchains # Must contain toolchains
│ │── mipsel-gcc4.9-crosstool-ng
│ │── baikal-gcc5.2
│ └── .....
├── docker_image
│ └── Dockerfile # Dockerfile for building docker image
└── Readme.md
Install docker and read this readme completely before start
Clone this repo and cd into it.
Unpack your sysroot in chr/sysroots/my_sysroot
Install additional toolchains in chr/toolchains/my_custom_toolchain
Run
./build.sh config_name build_name
chr/chromium/src/out/. You can ommit it and in that case same value as config_name will be used.Example:
./build.sh 56-gcc5.4
After build finishes you can make archive with build result:
cd chr/chromium/src/out/my_build_name
tar -cvzf /dest/dir/my-custom-chromium-build.tar.gz --exclude='./obj' --exclude='./gen' --exclude='./clang_x86_v8_mipsel' --exclude='./x64' --exclude='./clang_x86' .
builder(uid=1000). Thus it is recommended to clone repo and run all commands with host user having same uid value. Also you can create new user in image having desired uid.chr/toolchains/chr/configs were tested with "baikal-rootfs-chromedeps" sysyroot that can be downloaded at [todo add link to ftp]build.sh called it will automatically download chromium sources to chr/chromium/src. Chromium repo have huge size(about 17GB), so it may take long time.Content type
Image
Digest
Size
782.8 MB
Last updated
over 9 years ago
docker pull comsgn/mipschrome