Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/dev2forge/bridgex/llms.txt

Use this file to discover all available pages before exploring further.

Bridgex 0.2.1 can be installed in three ways: through the Rust toolchain using Cargo (recommended for all platforms), through pip on Windows and macOS, or by downloading the prebuilt Linux binary from SourceForge. Choose the tab below that matches your preferred installation method.
pip install bridgex is only supported on Windows and macOS. The PyPI wheel bundles a compiled Rust binary for those platforms. Linux users must use the SourceForge binary or build from source with Cargo.

Requirements

  • A Rust toolchain with cargo installed. The stable Rust channel is recommended.
  • On Linux, several system libraries are required before building (see the Linux system dependencies section below).

Install from crates.io

The simplest way to install the latest published release is directly from crates.io:
cargo install bridgex
Once installed, launch the application from any terminal:
bridgex

Build from Source

Clone the repository and navigate to the Rust crate directory, then build or run the application:
1

Clone the repository

git clone https://github.com/Dev2Forge/bridgex.git
2

Navigate to the crate directory

cd bridgex/src/bridgex
3

Build a release binary

cargo build --release
The compiled binary will be at ./target/release/bridgex.
4

Run or install locally

./target/release/bridgex

Linux System Dependencies

When building from source on a Debian/Ubuntu-based Linux system, you must install the following packages before running cargo build. The CI workflow uses these exact packages:
sudo apt update

base_packages="build-essential libssl-dev pkg-config libglib2.0-dev libgtk-3-dev \
  libudev-dev libxdo-dev libfreetype6-dev libfontconfig1-dev libegl1-mesa-dev \
  libgl1-mesa-dev libwayland-egl1-mesa libgles2-mesa-dev libx11-dev libxcursor-dev \
  libxrandr-dev libxi-dev libxkbcommon-dev libwayland-dev cmake"

sudo apt install -y $base_packages libwebkit2gtk-4.1-dev || \
  sudo apt install -y $base_packages libwebkit2gtk-4.0-dev
The installer attempts libwebkit2gtk-4.1-dev first and falls back to libwebkit2gtk-4.0-dev for older distributions that do not carry the 4.1 version. Both variants satisfy the build requirements.
The full list of required packages is:
PackagePurpose
build-essentialC/C++ compiler toolchain
libssl-devTLS support
pkg-configBuild system helper
libglib2.0-devGLib base library
libgtk-3-devGTK 3 UI toolkit
libudev-devDevice event support
libxdo-devX11 automation library
libfreetype6-devFont rendering
libfontconfig1-devFont configuration
libegl1-mesa-devEGL (GPU surface)
libgl1-mesa-devOpenGL
libwayland-egl1-mesaWayland EGL integration
libgles2-mesa-devOpenGL ES 2
libx11-devCore X11 library
libxcursor-devCursor theming
libxrandr-devDisplay configuration
libxi-devX Input extension
libxkbcommon-devKeyboard handling
libwayland-devWayland protocol
cmakeBuild system for native deps
libwebkit2gtk-4.1-dev or libwebkit2gtk-4.0-devWebKit2GTK web renderer

Build docs developers (and LLMs) love