Show you remit and github side-by-side, so you can review comfortably.
Because the other two only work on macOS and one bold developer had to use Linux.
Note
This flow isn't ideal. There's an issue to build a Dialog that prompts for Remit's URL and Token.
- Run qt-remit. The left pane will show an example page. That's fine, we'll fix that later.
- Log into Github in the right pane
- Close qt-remit
- Find the config file and set the Remit URL and token. qt-remit uses QStandardPaths::AppConfigLocation
- on macOS, the file is at
~/Library/Preferences/qt-remit/config.ini
- on Linux, the file is at
~/.config/qt-remit/config.ini
- on macOS, the file is at
- Open qt-remit again
- Go to the remit settings and click "Sign in with Github"
You'll need C++ development dependencies. Most linux distros have a package/pattern/package group for that:
- Ubuntu:
sudo apt install build-essential
- Arch:
sudo pacman -S base-devel
- OpenSUSE Tumbleweed:
sudo zypper in -t pattern devel_C_C++
- macOS:
xcode-select --install
. If you have git on your mac, this is done.
You'll also need Qt-development dependencies for Qt6.6. Make sure you install:
- Core
- QWidgets
- QWebEngineCore
- QWebEngineWidgets
- qmake
I installed Qt 6.6.1 through the Qt OSS online installer. If you use that, remember to check "Qt WebEngine" in the "Additional Libraries" for the Qt version you're installing. Just selecting 'Qt for Desktop development' is not enough.
On macOS: brew install qt
Qt SDK Installation through linux package managers is untested (read: Please try setting this up using brew if you have the time!)
- Clone the repository
- Create a folder for the build output.
cmake -S path/to/qt-remit/ -O path/to/build/folder
cd
into the build output foldermake
This should generate a binary you can put somewhere on your path and run, as long as it can find a Qt6 that has the WebEngineWidgets installed.
On OpenSUSE Tumbleweed, sudo zypper in libQt6WebEngineWidgets6
gets you everything you need, since it depends on everything else qt-remit depends on.
When building a package, make sure this is listed as a requirement.
On macOS, the build steps above produce an application package without an icon. Dropping that into your /Applications
folder should just work.
Yes.