Building
Build against system packages
By default, most dependencies are fetched with CPM.cmake.
If you prefer to use system-installed packages instead of downloading them directly, configure CPM with one of these options:
CPM_USE_LOCAL_PACKAGES=ONCPM_LOCAL_PACKAGES_ONLY=ON
See the CPM reference for details.
Tip
Use CPM_LOCAL_PACKAGES_ONLY=ON when integrating with package managers such as Conan or vcpkg.
This ensures CPM won’t try to fetch sources remotely.
General dependencies
- Boost >=
1.83.0 - gRPC >=
1.51.1 - fmt >=
11.0.0 - Quill >=
10.0.0 - EnTT >=
3.15.0 - stdexec >=
daf12bcc46438f88b3c78212363f7b6531338780 - asio-grpc >=
3.3.0 - JSON for Modern C++ >=
3.11.0 - stb >=
f0569113c93ad095470c54bf34a17b36646bbbb5
CMake options
The build can be customized with several CMake options:
QUITE_BUILD_REMOTE_MANAGER
- Default:
ON - Description: Builds the remote-manager application.
- Introduced dependencies:
- CLI11 ≥
2.4.0
- CLI11 ≥
QUITE_BUILD_TEST_API
- Default:
ON - Description: Builds the C++ testing API.
QUITE_BUILD_PYTHON_TEST_API
- Default:
ON - Description: Builds the Python testing API module.
- Dependencies: Requires
QUITE_BUILD_TEST_API=ON. - Introduced dependencies:
- pybind11 ≥
3.0.0
- pybind11 ≥
See Python Usage for details.
QUITE_BUILD_PROBE_QT
- Default:
ON - Description: Builds the Qt probe.
- Introduced dependencies:
- Qt ≥
6.5.0
- Qt ≥
QUITE_INSTALL
- Default::
ON - Description:: Adds cmake install steps to targets.