Iridium is an open modification of the Chromium code base, with privacy being enhanced in several key areas. Automatic transmission of partial queries, keywords, metrics to central services is inhibited and only occurs with consent.
Some more information and binary downloads can be found at https://iridiumbrowser.de/ .
The repository is at git://git.iridiumbrowser.de/iridium-browser and https://github.com/iridium-browser/iridium-browser/ .
The easy way to build from source is to re-use the mechanisms of one's Linux distribution, that is, their build environment and description for chromium, and replacing the source tarball by the one from https://dl.iridiumbrowser.de/source/ .
Reporting bugs and issues
Use the Iridium Browser issue tracker on GitHub to report your findings.
The following is a collection of steps, saved here primarily as a note for ourselves. When starting off with the Git repository, the following preparatory steps may be needed:
- Download depot_tools and add it to your
gclient sync(this utility comes from depot_tools). For gclient, you need to have python 2(!) and python2-virtualenv. The sync command will not necessary complete successfully due to webrtc.
Download WebRTC if gclient did not do it for you. Google populates the Chromium
DEPSfile with a commit hash for WebRTC, and if there is no branch head which is exactly equal to the hash,
gclient syncbarfs about it. Then, you have to fetch the data manually:
` pushd third_party/webrtc/ git ls-remote origin | grep 0b2302e5e0418b6716fbc0b3927874fd3a842caf abcdef... refs/branch-heads/m78 git fetch origin refs/branch-heads/m78 git reset --hard FETCH_HEAD popd `
Undo the PATH change from 1, since depot_tools ships an untrusted copy of ninja.
From here on, steps apply to source builds of any kind:
The gn files in Iridium are edited to respect the
$CCetc. environment variables. These env vars _must_ always be set, so issue
export CC=gcc CXX=g++ AR=ar NM=nm(can pick any preferred toolchain, though).
Link up nodejs:
` mkdir -p third_party/node/linux/node-linux-x64/bin ln -s /usr/bin/node third_party/node/linux/node-linux-x64/bin/ `
Because chromium is too stupid to use pkg-config for wayland and xkbcommon, it needs to be manually specified. Issue
` export CFLAGS="-O2 -Wall $(pkg-config wayland-client xkbcommon --cflags)" export CXXFLAGS="$CFLAGS" gn gen '--args=custom_toolchain="//build/toolchain/linux/unbundle:default" host_toolchain="//build/toolchain/linux/unbundle:default" use_custom_libcxx=false is_debug=false enable_nacl=false use_swiftshader_with_subzero=true is_component_ffmpeg=true use_cups=true use_aura=true concurrent_links=1 symbol_level=1 blink_symbol_level=0 use_kerberos=true enable_vr=false optimize_webui=false enable_reading_list=false use_pulseaudio=true link_pulseaudio=true is_component_build=false use_sysroot=false fatal_linker_warnings=false use_allocator="tcmalloc" fieldtrial_testing_like_official_build=true use_gold=true use_gnome_keyring=false use_unofficial_version_number=false use_lld=false use_vaapi=true use_sysroot=false treat_warnings_as_errors=false enable_widevine=false use_dbus=true use_system_harfbuzz=true use_system_freetype=true enable_hangout_services_extension=true enable_vulkan=true rtc_use_pipewire=true rtc_link_pipewire=true rtc_pipewire_version="0.3" is_clang=false icu_use_data_file=false proprietary_codecs=true ffmpeg_branding="Chrome"' out/Release `
There are a number of dependencies, and they may vary across operating systems. The gn command fails if there are unmet dependencies, and it will tell you which. Install and repeat the gn command as needed. Consult your distribution's package manager. On openSUSE, it is possible to use
zypper si -d chromiumto do that in a single shot.
LD_LIBRARY_PATH=$PWD/out/Release ninja -C out/Release chrome chromedriver.