# LibreWolf This repository contains all the patches and theming that make up LibreWolf, as well as the LibreWolf preferences (in [settings/](./settings)) and the scripts and Makefile to build LibreWolf. This is a re-design of the LibreWolf build system, called LibreWolf MaKe, or just lwmk for short. It is a fork of the LibreBoot MaKe (lbmk) build system, which Libreboot uses to build coreboot images. It was decided that this design is beneficial for LibreWolf, as it offers advanced features by comparison, such as: * Automatic caching of sources when downloading (Git repositories are used) * Redundant repository links are possible, for reliability in the future * Ability to declare custom git submodules, regardless of whether a project uses them; actual git submodules are unused. The lwmk design allows systematic patching and revision resets on submodules. * Ability to download files as submodules as well, hash-checking everything. Both git repositories and files are checked relentlessly, even when using local cache, to ensure integrity and general reproducibility. * Multi-tree design: projects like firefox can be build single- or multi-tree. In lwmk nomenclature, this means that a given project can have multiple targets, or just build one target. Multi-tree is preferred, where feasible; in lwmk, you can specify multiple revisions of Firefox, and multiple targets off of each tree name on the given revision. An application for this might be providing LibreWolf along with variants like LibreWolf-Hellfire, or more opiniated forks of LibreWolf that mostly just change a few configs. * Completely generalised design. The `mk` script and `include/` directory do not generally contain project-specific build logic. Each project can use mkhelpers to specify custom steps e.g. pre-configure, post-build, and so on, much like on a BSD ports system. This design is reminiscent of a Linux distro, because indeed it was first implemented for Libreboot which is a coreboot distro; this design generalises the downloading, patching and building of any source tree. It is highly flexible and configurable. * Ease of use. Despite high configurability, the overarching philosophy is like that for OpenBSD: Knobs are for nobs. We want everything to be as simple as possible for the user, with sane defaults for everything. The design of the entire build system reflects this philosophy. The lwmk build system can generate binaries on the spot, and it does so using out-of-tree building. It can also generate clean source tarballs of sources e.g. Firefox sources. The multi-tree nature of LibreWolf MaKe mean that you can support any number of actual Firefox derivatives. This build system is designed for use with the LibreWolf project, but it is intended that this design be used on every other Firefox fork; perhaps the projects can even work with each other, or there can be another project that uses this design and generalises all of the Mozilla forks. This might be useful for Linux distros, which can then just do something like: ./mk -b firefox This would build every variant of Firefox in lwmk. Every defined tree, at each defined revision, for each target defined referencing each tree. The best part: because it uses the same design from the Libreboot build system, there are *no make files* in the tree, until you run `./mk -f`. One caveat: this is a very much Linux- and BSD-brained build system. It is NOT designed to run on others like Windows or Mac. That being said, it can generate source tarballs of Firefox and its variants such as LibreWolf. These tarballs are cross-platform, and that will always be the case.