mirror of
https://codeberg.org/librewolf/source.git
synced 2025-01-03 11:20:11 -05:00
56 lines
1.7 KiB
Markdown
56 lines
1.7 KiB
Markdown
## Note: this part of the build is mostly done, but still requires a patch.
|
|
|
|
Next, we create ourselves a build folder and extract the tarball.
|
|
```
|
|
mkdir build
|
|
cd build
|
|
tar xf ../librewolf-$(version).source.tar.gz
|
|
```
|
|
Next step, if you have not done so already, you must create the build environment:
|
|
```
|
|
cp librewolf-$(version)/lw-assets/bootstrap.py .
|
|
python3 --no-interactive bootstrap.py --application-choice=browser
|
|
```
|
|
It takes about an hour for me to complete, but it needs to be done only once. This step might fail and cause problems. Why Mozilla has no separate 'install-buildenv.py' is a bit beyond me. I would have liked to be able to set up the build environment in one step, in a second step checkout the entire mozilla source, or in our case, use our own source.
|
|
|
|
Now we're ready to actually build LibreWolf:
|
|
```
|
|
cd librewolf-$(version)
|
|
./mach build
|
|
```
|
|
Also takes me an hour. Then, we can run it:
|
|
```
|
|
./mach run
|
|
```
|
|
Or make a package:
|
|
```
|
|
./mach package
|
|
```
|
|
|
|
## Building LibreWolf source tarball:
|
|
|
|
You don't need the build environment for this. If you don't have write access, just:
|
|
```
|
|
git clone https://gitlab.com/librewolf-community/browser/source.git
|
|
cd source
|
|
make all
|
|
```
|
|
If you **do** have write access, we're first gonna check for a newer version of Firefox:
|
|
```
|
|
git clone git@gitlab.com:librewolf-community/browser/source.git
|
|
cd source
|
|
make check
|
|
```
|
|
If there is a new version, it's a good time to git commit and trigger a CI build job.
|
|
```
|
|
git commit -am v$(cat version) && git push
|
|
```
|
|
To build the source archive:
|
|
```
|
|
make all
|
|
```
|
|
If you have a working build environment, you can build librewolf with:
|
|
```
|
|
make librewolf
|
|
```
|
|
This extracts the source, and then tries to `./mach build && ./mach package`.
|