54387fd628
add remaining patches from common to allow switching over to source See merge request librewolf-community/browser/source!20 |
||
---|---|---|
assets | ||
patches | ||
scripts | ||
submodules | ||
themes/browser | ||
.gitignore | ||
.gitlab-ci.yml | ||
.gitmodules | ||
LICENSE | ||
Makefile | ||
README.md | ||
README.md.in | ||
release | ||
version |
Active repositories and projects
List of browser build sub projects. These are the locations where people have their repositories and build artifacts.
Currently active build repositories:
- Linux: Flatpak, AppImage, Arch and other Linux builds of the LibreWolf browser.
- Bsys5: deb for mint,fedora,ubuntu; dmg for macOS.
- macOS: The macOS build of LibreWolf.
- Windows: LibreWolf builds for Windows.
- Gentoo:
- OpenBSD:
- Flatpak:
- fedora: bgstack15
- Debian: bgstack15
- Arch:
Currently active forks:
- FireDragon: https://github.com/dr460nf1r3/firedragon-browser
LibreWolf build instructions
First, let's download the latest tarball. This tarball is the latest produced by the CI. You can also check the sha256sum of the tarball there.
So here is how build LibreWolf for Linux:
tar xf <tarball>
cd <folder>
make setup-wasi bootstrap build package run
How to make a patch:
The easiest way to make patches is to go to the LibreWolf source folder:
cd librewolf-$(cat version)
git init
git add <path_to_file_you_changed>
git commit -am initial-commit
git diff > ../mypatch.patch
We have Gitter / Matrix rooms, and on the website we have links to the various issue trackers.
Building LibreWolf with git:
- Clone the git repository via https:
git clone --recursive https://gitlab.com/librewolf-community/browser/source.git
or ssh:
git clone --recursive git@gitlab.com:librewolf-community/browser/source.git
cd into it, build the LibreWolf tarball, bootstrap the build environment, and finally, perform the build:
cd source
make all
make bootstrap
make build
After that, you can either build a tarball from it, or run it:
make package
make run
How to create a patch for problems in Mozilla's Bugzilla.
Well, first of all:
- Create an account.
- Handy link: Bugs Filed Today.
- The essential: Firefox Source Tree Documentation.
Now that you have a patch in LibreWolf, that's not enough to upload to Mozilla. See, Mozilla only accepts patches against Nightly. So here is how to do that:
hg clone https://hg.mozilla.org/mozilla-unified
cd mozilla-unified
hg update
MOZBUILD_STATE_PATH=$HOME/.mozbuild ./mach --no-interactive bootstrap --application-choice=browser
./mach build
./mach run
Now you can apply your patch to Nightly:
patch -p1 -i ../mypatch.patch
Now you let Mercurial create the patch:
hg diff > ../my-nightly-patch.patch
And it can be uploaded to Bugzilla.
(copy of Mozilla readme) Now the fun starts
Time to start hacking! You should join us on Matrix, say hello in the Introduction channel, and find a bug to start working on. See the Firefox Contributors’ Quick Reference to learn how to test your changes, send patches to Mozilla, update your source code locally, and more.
Hey, I'm using a Mac or Windows :(
We understand, life isn't always fair 😺. The same steps as above do apply, you'll just have to walk through the beginning part of the guides for MacOS, Windows. To build on Windows is not very well tested. The cross-compiled Mac .dmg files are also relatively new. It should work, perhaps with the exception of the make setup-wasi
step. Help testing with these targets is always welcome.