forked from Silverfish/proton-bridge
d3f9756bdb
GODT-1714: link the update check mecanism [skip-ci] GODT-1714: bind update check notification [skip-ci] GODT-1714: Send the CheckFinishEvent in defer to be sure it never loop for eternity GODT-1714: simplify the BRIDGE_APP_VERSION configuration [skip-ci] GODT-1714: Fix CheckUpdateAndNotify based on what already exists GODT-1714: Restore LandingPage and ReleaseNotesPage links [skip-ci] Other: Cactch case in CMake where BRIDGE_APP_VERSION is not filled [skip-ci]
Prerequisite
Linux (debian and derivates)
sudo apt install build-essential
sudo apt install tar curl zip unzip
sudo apt install linux-headers-$(uname -r)
sudo apt install mesa-common-dev libglu1-mesa-dev
macOS & WIndows
Coming soon...
Define QT6DIR
export QT6DIR=/opt/Qt/6.3.1/gcc_64
install vcpkg and define VCPKG_ROOT
git clone https://github.com/Microsoft/vcpkg.git
./vcpkg/bootstrap-vcpkg.sh
export VCPKG_ROOT=$PWD/vcpkg
install grpc & protobuf
./vcpkg install grpc
Building
A simple script is provided that run the appropriate CMake command.
./build.sh
Running
Simply run from the cmake build folder (cmake-build-debug by default)
./bridge-gui
bridge-gui will launch the bridge executable that it will try to locate in
- The working directory.
- The application directory.
cmd/Desktop-Bridge/,../cmd/Desktop-Bridge/,../../cmd/Desktop-Bridge(up to five parent folders above the current folder are inspected).
you can specify the location of the bridge executable using the -b or
--bridge-exe-path command-line parameter:
./bridge-gui -b "~/bin/bridge"
you can also ask bridge-gui to connect to an already running instance of bridge
using the -a or --attach command line parameter.
./bridge-gui -a