jplcz_reloco provides native metadata for Conan 2, a vcpkg overlay port,
and direct CPM.cmake integration. Every integration exposes the same CMake
target:
find_package(jplcz_reloco CONFIG REQUIRED)
target_link_libraries(my_target PRIVATE jplcz_reloco::reloco)The package is header-only and requires C++17 or later. It has no third-party dependencies.
The repository root contains a Conan 2 recipe. Create it in the local Conan cache from a checkout:
conan profile detect --force
conan create . --build=missingThe resulting reference is jplcz_reloco/0.1.0. A consuming
conanfile.txt can request it and generate CMake integration:
[requires]
jplcz_reloco/0.1.0
[generators]
CMakeDeps
CMakeToolchain
[layout]
cmake_layoutInstall dependencies and configure the consumer with Conan's generated toolchain:
conan install . --build=missing -s compiler.cppstd=17
cmake --preset conan-release
cmake --build --preset conan-releaseFor a single-config generator without Conan-generated presets, pass
-DCMAKE_TOOLCHAIN_FILE=<output-folder>/conan_toolchain.cmake and an explicit
CMAKE_BUILD_TYPE when configuring CMake.
The recipe uses Conan's header-library package type and clears the package ID,
so operating-system, architecture, compiler, and build-type differences do not
produce duplicate binary packages. CMakeDeps generates
jplcz_relocoConfig.cmake with the canonical
jplcz_reloco::reloco target.
The repository contains a checkout-local overlay port at
packaging/vcpkg/ports/jplcz-reloco. Install it with:
vcpkg install jplcz-reloco \
--overlay-ports=/absolute/path/to/reloco/packaging/vcpkg/portsConfigure a consumer through the vcpkg toolchain:
cmake -S . -B build \
-DCMAKE_TOOLCHAIN_FILE="$VCPKG_ROOT/scripts/buildsystems/vcpkg.cmake"
cmake --build buildThe consumer then uses the standard find_package and target shown at the top
of this guide. The vcpkg package name uses a hyphen because vcpkg port names do
not use underscores; this does not change the CMake package or target names.
The included overlay deliberately packages the current checkout. This makes
local development and pinned source checkouts reproducible without embedding a
moving Git reference in the port. A registry submission should replace the
local SOURCE_PATH with vcpkg_from_github, an immutable release tag, and its
verified SHA-512 archive hash.
Pin a release tag or commit in the consuming project:
include(cmake/CPM.cmake)
CPMAddPackage(
NAME jplcz_reloco
GITHUB_REPOSITORY jplcz/reloco
GIT_TAG <release-tag-or-commit>
OPTIONS
"JPLCZ_RELOCO_BUILD_TESTS OFF"
"JPLCZ_RELOCO_BUILD_HEADER_CHECKS OFF"
"JPLCZ_RELOCO_INSTALL OFF"
)
target_link_libraries(my_target PRIVATE jplcz_reloco::reloco)Use an immutable tag or full commit hash rather than a moving branch. The development and installation options already default to off when the project is embedded, but listing them explicitly keeps dependency behavior visible and stable if the top-level project changes its cache.
For a local checkout, replace GITHUB_REPOSITORY and GIT_TAG with:
SOURCE_DIR "${CMAKE_SOURCE_DIR}/third_party/jplcz_reloco"No CPM-specific target alias is needed; CPMAddPackage delegates to the
project's normal add_subdirectory integration.
Other dependency managers that consume CMake projects directly can use the
same add_subdirectory interface documented in
README: Add jplcz_reloco. Managers that
consume installed CMake config packages can use the normal installation
described there too.
Standalone, top-level configurations with JPLCZ_RELOCO_INSTALL=ON (the
default) also enable CPack. Build and package with:
cmake -S . -B build \
-DJPLCZ_RELOCO_BUILD_TESTS=OFF \
-DJPLCZ_RELOCO_BUILD_HEADER_CHECKS=OFF
cmake --build build
cpack --config build/CPackConfig.cmakeArchive generators (TGZ, ZIP) are always available. DEB and RPM
generators are added automatically when dpkg-deb or rpmbuild are found on
the host; since the package is header-only, both are built as
architecture-independent (all/noarch) packages. Run
cpack --config build/CPackSourceConfig.cmake for a source archive, which
excludes VCS metadata and build directories.
Installing any generated package places headers under include/ and CMake
package files under share/cmake/jplcz_reloco/, matching the layout
produced by cmake --install; see
README: Add jplcz_reloco for how
consumers locate the installed package. scripts/check-cpack-package.sh
builds every available generator and verifies the archive package's contents.