Skip to content

iridium-browser/iridium-browser

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

90 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Iridium Browser

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/ .

Development

The repository is at git://git.iridiumbrowser.de/iridium-browser and https://github.com/iridium-browser/iridium-browser/ .

To build from source, it is advised 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/ .

Be aware there are different types of source code collections:

The current Git branch you are looking at and reading this README.rst from is in the tarball state.

Reporting bugs and issues

Use the Iridium Browser issue tracker on GitHub to report your findings.

Build steps for chromium-git state

The following is a collection of steps, saved here primarily as a note for ourselves. When starting off with the chromium-git state, the following preparatory steps may be needed:

  1. Download depot_tools and add it to your $PATH environment variable.
  2. Issue command: 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.
  3. Download WebRTC if gclient did not do it for you. Google populates the Chromium DEPS file with a commit hash for WebRTC, and if there is no branch head which is exactly equal to the hash, gclient sync barfs about it. Then, you have to fetch the data manually:

  4. Undo the PATH change from 1, since depot_tools ships an untrusted copy of ninja.

From here on, steps apply to both source builds of any kind, that is, chromium-git or tarball state.

Steps for tarball state

  1. The gn files in Iridium are edited to respect the $CC etc. environment variables. These env vars _must always be set, so issue

    or

    (can pick any preferred toolchain, though).

  2. Link up nodejs:

  3. Generate Makefilery:

    Note that gn embodies the environment variables' values (CC, CFLAGS, etc.) into Makefiles, so upon change of any of those variables, gn needs to be re-run.

  4. 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 chromium to do that in a single shot. On Debian, there is something like apt-get build-dep.
  5. Execute this to build:

    Because chromium is too ignorant to look for moc in the right place and name, or query some qt utility for the desired info, the path to it needs to be manually specified.

  6. The just-built executable can be run thus

Installation procedure

There is no "install" target. Thanks, Google. Every distro has to roll their own install procedure. For example,

This is why it was mentioned in one of the previous sections that you will have to re-use/leverage/adapt the chromium build recipe that your distro had.

About

Iridium Browser source code

Resources

License

BSD-3-Clause, BSD-3-Clause licenses found

Licenses found

BSD-3-Clause
LICENSE
BSD-3-Clause
LICENSE.chromium_os

Code of conduct

Stars

Watchers

Forks

Packages

No packages published