libscid can be used from a release archive or installed from a source checkout. The release archives are the easiest way to consume the library in another project; source installation is useful when developing libscid itself or when a prebuilt archive is not available for the target platform.
Pick the archive for your platform from the GitHub release assets:
libscid-cpp__<version>__linux.tar.gzlibscid-cpp__<version>__macos-arm.tar.gzlibscid-cpp__<version>__windows.tar.gzFor example:
The installation is relocatable for normal CMake package discovery. Point CMAKE_PREFIX_PATH at the extracted directory:
A release archive contains:
include/: installed public headers.lib/: compiled libscid libraries and CMake package files under lib/cmake/libscid-cpp.share/doc/libscid-cpp/COPYING: the GNU GPL v2 licence text.share/doc/libscid-cpp/README.md: the release README.share/doc/libscid-cpp/examples/: standalone example projects and fixtures.share/doc/libscid-cpp/html/: generated API documentation when built into the package archive.The package exports these CMake targets:
LibScidCpp::CoreLibScidCpp::DatabaseLibScidCpp::EcoLibScidCpp::SpellingConfigure, build and install with an explicit prefix:
To include generated API documentation in the install tree, enable docs and provide the documentation tools required by the build:
The repository also provides presets for local release and package builds:
Tests are disabled by default in top-level builds. Enable them explicitly:
Focused module test runs are also available after configuring with tests:
The documentation site is generated with Doxygen. If Doxygen, Graphviz and PlantUML are installed:
The generated HTML is written under _build/docs/doxygen/html.