mirror of
https://github.com/EFForg/rayhunter.git
synced 2026-04-26 07:29:59 -07:00
Better support for firmware-devel profile
Currently you have to override a bunch of paths to use firmware-devel when building the installer. This changes that, and adds a new FIRMWARE_PROFILE envvar that can be used to fix both rootshell and rayhunter-daemon paths at the same time. There is now also a new cargo command for building rootshell, similar to how building the daemon firmware works. I'm not sure what to do with make.sh. I have personally never used it.
This commit is contained in:
committed by
Markus Unterwaditzer
parent
2c30218743
commit
a3d0d8f4f9
@@ -14,12 +14,13 @@ You'll need to install [Tauri's dependencies](https://tauri.app/start/prerequisi
|
||||
|
||||
The GUI installer pulls in the CLI installer as a library. Like with the CLI installer, the firmware binary needs to be present and can be overridden with the same envvars. See `../installer/build.rs` for options.
|
||||
|
||||
For example, to build the firmware in development mode and then provide the path explicitly:
|
||||
For example, to build the firmware in development mode:
|
||||
|
||||
```bash
|
||||
cargo build-daemon-firmware-devel
|
||||
cargo build-rootshell-firmware-devel
|
||||
|
||||
(cd installer-gui && FILE_RAYHUNTER_DAEMON=$PWD/../target/armv7-unknown-linux-musleabihf/firmware-devel/rayhunter-daemon npm run tauri android build)
|
||||
(cd installer-gui && FIRMWARE_PROFILE=firmware-devel npm run tauri android build)
|
||||
```
|
||||
|
||||
## Building
|
||||
|
||||
Reference in New Issue
Block a user