mirror of https://github.com/EFForg/rayhunter.git synced 2026-04-26 07:29:59 -07:00

Files

Markus Unterwaditzer a3d0d8f4f9 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.

2026-01-30 21:09:12 +01:00

1.5 KiB

Raw Blame History

Rayhunter GUI Installer

This directory contains experimental work on a Rayhunter GUI installer based on Tauri.

Dependencies

Before building the GUI installer, you'll first need to install its dependencies.

Tauri Dependencies

You'll need to install Tauri's dependencies. In addition to Rust, you'll need Node.js/npm. If you're on Linux, also be sure to install the necessary system dependencies from your package manager.

Rayhunter CLI Installer

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:

cargo build-daemon-firmware-devel
cargo build-rootshell-firmware-devel

(cd installer-gui && FIRMWARE_PROFILE=firmware-devel npm run tauri android build)

Building

After preparing dependencies, the GUI installer can be built by:

Running npm install in this directory.
Running npm run tauri dev.

This will build the GUI installer in development mode. While this command is running, any changes to either the frontend or backend code will cause the installer to be reloaded or rebuilt.

You can also run npm run tauri build to create the final GUI installer artifacts for your OS as is done in CI.

1.5 KiB Raw Blame History