Installation
On this page you’ll learn how to install saucer through any of the officially supported ways.
Prerequisites
Section titled “Prerequisites”Before installing saucer, ensure your development environment meets the following requirements:
- A C++23 compatible compiler
- CMake (recommended installation method)
Dependencies
Section titled “Dependencies”Saucer relies on certain system-level dependencies to run.
These dependencies are usually pre-installed on the respective platform.
On Windows the WebView2 Runtime is required, which comes pre-installed since Windows 11.
Saucer uses Cocoa and WKWebView on MacOS, which are both part of the operating system.
Saucer supports both WebKitGtk and Qt (5 & 6) on Linux.
The default backend is WebKitGtk, but it can be configured through the saucer_backend
CMake-Option.
Both are well established in the Linux world and most systems have either of them installed already. In case you have neither installed on your system, you may refer to your distribution on how to install the following packages:
- gtk4
- webkitgtk-6.0
- qt5-qtwebengine
- qt5-qtwebchannel
- qt5-qtbase-gui
- qt5-qtbase
…or if you’re targetting Qt6:
- qt6-qtwebengine
- qt6-qtwebchannel
- qt6-qtbase-gui
- qt6-qtbase
Installation Methods
Section titled “Installation Methods”CPMAddPackage( NAME saucer VERSION v7.0.0 GIT_REPOSITORY "https://github.com/saucer/saucer")
target_link_libraries(${PROJECT_NAME} [PRIVATE|PUBLIC] saucer::saucer)
FetchContent_Declare( saucer GIT_REPOSITORY https://github.com/saucer/saucer GIT_TAG v7.0.0)
FetchContent_MakeAvailable(saucer)
target_link_libraries(${PROJECT_NAME} [PRIVATE|PUBLIC] saucer::saucer)
The GitHub Workflows automatically produce a pre-built artifact for Windows that you can link against manually.
TypeScript
Section titled “TypeScript”For those who plan on using saucer for serving their own frontend, we recommend to install the @saucer-dev/types
package,
which provides typed abstractions over all saucer functions.