0
Fork 0
mirror of https://codeberg.org/librewolf/source.git synced 2024-12-22 13:43:04 -05:00
LibreWolf/README.md.in

97 lines
4 KiB
Markdown
Raw Normal View History

2022-03-08 08:37:52 -05:00
## 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:
2022-03-09 06:35:55 -05:00
* fedora: bgstack15 version
* Debian: bgstack15 version
2022-03-08 08:37:52 -05:00
* Arch:
Currently active forks:
* FireDragon: https://github.com/dr460nf1r3/firedragon-browser
2022-02-03 04:58:11 -05:00
## LibreWolf build instructions
2022-02-03 04:17:35 -05:00
2022-02-05 15:09:43 -05:00
First, let's **[download the latest tarball](https://gitlab.com/librewolf-community/browser/source/-/jobs/artifacts/main/raw/librewolf-__VERSION__-__RELEASE__.source.tar.gz?job=Build)**. This tarball is the latest produced by the [CI](https://gitlab.com/librewolf-community/browser/source/-/jobs). You can also check the sha256sum of the tarball there.
2022-02-09 07:10:41 -05:00
So here is how build LibreWolf for Linux:
2022-02-03 04:57:05 -05:00
```
tar xf <tarball>
cd <folder>
2022-02-28 18:18:27 -05:00
make setup-wasi bootstrap build package run
2022-02-03 04:57:05 -05:00
```
2022-02-03 04:58:11 -05:00
#### How to make a patch:
2022-02-03 04:57:05 -05:00
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:
2022-02-03 04:17:35 -05:00
1. Clone the git repository via https:
```
git clone --recursive https://gitlab.com/librewolf-community/browser/source.git
```
or ssh:
2022-02-03 04:17:35 -05:00
```
git clone --recursive git@gitlab.com:librewolf-community/browser/source.git
```
2022-02-03 06:47:16 -05:00
cd into it, build the LibreWolf tarball, bootstrap the build environment, and finally, perform the build:
2022-02-03 04:17:35 -05:00
```
cd source
make all
make bootstrap
make build
```
2022-02-03 04:26:16 -05:00
After that, you can either build a tarball from it, or run it:
```
make package
make run
```
2022-02-03 05:54:09 -05:00
#### How to create a patch for problems in Mozilla's [Bugzilla](https://bugzilla.mozilla.org/).
2022-02-03 05:20:10 -05:00
Well, first of all:
* [Create an account](https://bugzilla.mozilla.org/createaccount.cgi).
* Handy link: [Bugs Filed Today](https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Bugs%20Filed%20Today&sharer_id=1&list_id=15939480).
* The essential: [Firefox Source Tree Documentation](https://firefox-source-docs.mozilla.org/).
2022-02-03 05:54:09 -05:00
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:
2022-02-03 05:20:10 -05:00
```
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
```
2022-02-03 05:54:09 -05:00
And it can be uploaded to Bugzilla.
2022-02-03 05:25:38 -05:00
2022-02-03 05:32:28 -05:00
##### *(copy of Mozilla readme)* Now the fun starts
2022-02-03 05:25:38 -05:00
Time to start hacking! You should join us on [Matrix](https://chat.mozilla.org/), say hello in the [Introduction channel](https://chat.mozilla.org/#/room/#introduction:mozilla.org), and [find a bug to start working on](https://codetribute.mozilla.org/). See the [Firefox Contributors Quick Reference](https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html#firefox-contributors-quick-reference) to learn how to test your changes, send patches to Mozilla, update your source code locally, and more.
2022-02-03 06:34:45 -05:00
#### Hey, I'm using a Mac or Windows :(
2022-02-28 18:18:27 -05:00
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](https://firefox-source-docs.mozilla.org/setup/macos_build.html), [Windows](https://firefox-source-docs.mozilla.org/setup/windows_build.html). 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.