mirror of
https://github.com/morgan9e/helium
synced 2026-04-15 00:44:06 +09:00
@@ -79,7 +79,10 @@ dpkg-buildpackage -b -uc
|
||||
|
||||
where `PACKAGE_TYPE_HERE` is one of the packaging types listed above. Packages will appear under `build/`
|
||||
|
||||
**NOTE**: If the build fails at any point, it can be fixed by removing `build/src` and re-running the build instructions. This will clear out all the code used by the build, and any files generated by the build. However, if the build fails during the `ninja` command during `dpkg-buildpackage`, you can use `dpkg-buildpackage -b -uc -nc` to resume building.
|
||||
**NOTE**: If the build fails, you must take additional steps before re-running the build:
|
||||
|
||||
* If the build fails while downloading the Chromium source code, it can be fixed by removing `build/download_cache` and re-running the build instructions.
|
||||
* If the build fails at any other point, it can be fixed by removing `build/src` and re-running the build instructions. This will clear out all the code used by the build, and any files generated by the build. However, if the build fails during the `ninja` command during `dpkg-buildpackage`, you can use `dpkg-buildpackage -b -uc -nc` to resume building.
|
||||
|
||||
### Building via source package
|
||||
|
||||
@@ -148,7 +151,10 @@ py ungoogled_packaging\package.py
|
||||
|
||||
A zip archive will be created in `build\src`
|
||||
|
||||
**NOTE**: If the build fails during `build.py` or earlier, it can be fixed by removing `build\src` and re-running the build instructions. This will clear out all the code used by the build, and any files generated by the build.
|
||||
**NOTE**: If the build fails, you must take additional steps before re-running the build:
|
||||
|
||||
* If the build fails while downloading the Chromium source code (which is during `build.py`), it can be fixed by removing `build\download_cache` and re-running the build instructions.
|
||||
* If the build fails at any other point during `build.py`, it can be fixed by removing `build\src` and re-running the build instructions. This will clear out all the code used by the build, and any files generated by the build.
|
||||
|
||||
## macOS
|
||||
|
||||
@@ -179,7 +185,10 @@ cd build/src
|
||||
|
||||
A `.dmg` should appear in `build/src/ungoogled_packaging/`
|
||||
|
||||
**NOTE**: If the build fails at any point, it can be fixed by removing `build/src` and re-running the build instructions. This will clear out all the code used by the build, and any files generated by the build.
|
||||
**NOTE**: If the build fails, you must take additional steps before re-running the build:
|
||||
|
||||
* If the build fails while downloading the Chromium source code, it can be fixed by removing `build/download_cache` and re-running the build instructions.
|
||||
* If the build fails at any other point after downloading, it can be fixed by removing `build/src` and re-running the build instructions. This will clear out all the code used by the build, and any files generated by the build.
|
||||
|
||||
## Arch Linux
|
||||
|
||||
@@ -294,7 +303,10 @@ cd build/src
|
||||
|
||||
A compressed tar archive will appear in `build/src/ungoogled_packaging/`
|
||||
|
||||
**NOTE**: If the build fails during `build.sh` or earlier, it can be fixed by removing `build/src` and re-running the build instructions. This will clear out all the code used by the build, and any files generated by the build.
|
||||
**NOTE**: If the build fails, you must take additional steps before re-running the build:
|
||||
|
||||
* If the build fails while downloading the Chromium source code (during `build.sh`), it can be fixed by removing `build/download_cache` and re-running the build instructions.
|
||||
* If the build fails at any other point after downloading, it can be fixed by removing `build/src` and re-running the build instructions. This will clear out all the code used by the build, and any files generated by the build.
|
||||
|
||||
### Building an AppImage
|
||||
|
||||
|
||||
Reference in New Issue
Block a user