Quick install
The fast path from nothing to a running ClikaRT program. For per-platform depth, IDE setup and the full failure catalog, see Complete installation.
0. Prerequisites
A C++17 compiler and CMake 3.20 or newer:
sudo apt install build-essential cmake # Debian/Ubuntu
brew install cmake # macOS; compiler: xcode-select --install
winget install Kitware.CMake # Windows; compiler: Visual Studio Build Tools
1. Get the bundle
Extract the archive for your platform (Get ClikaRT has the download and checksum commands) and remember where it is:
tar -xf ClikaRT_linux_x86_64-<version>.tar.xz
export CLIKART_BUNDLE_DIR="$PWD/ClikaRT_linux_x86_64-<version>"
ls "$CLIKART_BUNDLE_DIR"
The ls is the success check: bin/, cmake/, include/, lib/ and examples/ are among the entries. A new terminal loses the export; re-run it there, every command below uses it. On Windows, run these in PowerShell (tar is built in since Windows 10).
2. Run a pre-built example
The fastest proof the bundle works. Desktop archives ship pre-built example binaries; run one in place. Nothing gets installed, and no GPU or driver is needed:
"$CLIKART_BUNDLE_DIR"/examples/bin/version_00_hello_world
ClikaRT 0.4.6
On a platform without pre-built binaries, skip to step 3. On a Jetson, extract the linux_arm64 archive; its binaries run out of the box there, as on any other arm64 Linux machine.
3. Build the version example yourself
The same proof through your own toolchain. The three flags, once: -S is the source directory, -B is the build directory, and ClikaRT_DIR tells CMake where the bundle's cmake/ folder is.
cmake -S "$CLIKART_BUNDLE_DIR/examples/src/version" -B build-version \
-DClikaRT_DIR="$CLIKART_BUNDLE_DIR/cmake"
cmake --build build-version
./build-version/version_00_hello_world
ClikaRT 0.4.6
If something failed
cmake: command not found: step 0.tar: xz: Cannot execorxz: command not found: installxz-utils(Debian/Ubuntu) orxz.Could not find a package configuration file provided by "ClikaRT":ClikaRT_DIRis wrong, or theexportwas lost to a new terminal. An error naming a bare/cmakepath means the variable expanded empty; re-run theexportfrom step 1.- The binary is missing after an MSVC build: it lands in a configuration subdirectory,
build-version\Debug\version_00_hello_world.exe.
The install works. Write your first program.