From source

The canonical install path. Supported platforms: Linux x86_64 and arm64.

git clone https://github.com/pineforge-4pass/pineforge-engine.git
cd pineforge-engine
cmake -B build -DCMAKE_BUILD_TYPE=Release
cmake --build build -j
sudo cmake --install build --prefix /usr/local

Useful CMake options

Option	Default	Effect
`CMAKE_BUILD_TYPE`	`Release`	Set to `Debug` for assertions and unstripped symbols.
`PINEFORGE_BUILD_TESTS`	`ON`	Build the `ctest` suite (several hundred test binaries). Disable in package builds.
`PINEFORGE_BUILD_TUTORIAL`	`ON`	Build `tutorial/macd/strategy.so`.
`PINEFORGE_BUILD_CORPUS_STRATEGIES`	`OFF`	Build one `strategy.so` per probe of the parity corpus submodule (`git submodule update --init corpus`; 312 probes at its pinned commit).
`PINEFORGE_ENABLE_COVERAGE`	`OFF`	Instrument runtime + tests for source coverage (Clang/GCC).
`PINEFORGE_BUILD_EXAMPLES`	`OFF`	Build the Pine-free hosts of `examples/native/` and their `example_*` CTest rows.
`PINEFORGE_BUILD_SOURCE_LAYER`	`ON`	`OFF` builds the kernel alone; the Pine adapter headers are not installed.
`PINEFORGE_BUILD_LIVE_RUNNER`	`OFF`	Build the native `pineforge-live` runner (SQLite3, libcurl, OpenSSL); see `runner/README.md`.
`CMAKE_INSTALL_PREFIX`	`/usr/local`	Install root.

Install layout

${prefix}/
├── lib/
│   ├── libpineforge.a          # kernel + Pine adapter (PineForge::pineforge)
│   ├── libpineforge_kernel.a   # the kernel alone (PineForge::kernel)
│   └── cmake/PineForge/
│       ├── PineForgeConfig.cmake
│       ├── PineForgeConfigVersion.cmake
│       └── PineForgeTargets*.cmake
└── include/pineforge/
    ├── pineforge.h        # public C ABI
    ├── native_c_api.h     # C native-host API (included by pineforge.h)
    ├── version.h          # generated version macros
    ├── native_*.hpp       # kernel / native C++ API (see Public contract)
    ├── *.hpp              # the other C++ headers (no stability guarantee)
    ├── source/            # Pine adapter headers (internal; not in a kernel-only build)
    └── compat/pine/       # Pine adapter headers (internal; not in a kernel-only build)

Prebuilt tarballs

A release attaches the library prebuilt to its GitHub release. From 1.8.0, only Linux x86_64 and arm64 archives are published. Releases up to 1.7.0 also carry a macOS archive. For v1.3.0 they are pineforge-v1.3.0-linux-x86_64.tar.gz, pineforge-v1.3.0-linux-aarch64.tar.gz and pineforge-v1.3.0-macos-universal.tar.gz (one archive for arm64 and x86_64), each with a .sha256. A tarball unpacks to one directory, pineforge-v1.3.0-<platform>/, laid out as the install above (both archives, include/pineforge/, lib/cmake/PineForge/), with LICENSE, NOTICE and VERSION beside them:

curl -LO https://github.com/pineforge-4pass/pineforge-engine/releases/download/v1.3.0/pineforge-v1.3.0-linux-x86_64.tar.gz
curl -LO https://github.com/pineforge-4pass/pineforge-engine/releases/download/v1.3.0/pineforge-v1.3.0-linux-x86_64.tar.gz.sha256
sha256sum -c pineforge-v1.3.0-linux-x86_64.tar.gz.sha256   # macOS (for releases up to 1.7.0): shasum -a 256 -c
tar -xzf pineforge-v1.3.0-linux-x86_64.tar.gz

A CMake consumer finds it with -DCMAKE_PREFIX_PATH=$PWD/pineforge-v1.3.0-linux-x86_64 (CMake integration). The package config asks for Eigen 3.3 or later (find_dependency(Eigen3 3.3)): install it on Linux (libeigen3-dev on Debian and Ubuntu); for releases up to 1.7.0, the macOS tarball carries Eigen 3.4.0's headers and CMake package, which the same prefix finds.

Docker

This repository publishes no container image: from 1.8.0, a release attaches prebuilt static-lib tarballs, pineforge-vX.Y.Z-linux-x86_64.tar.gz and pineforge-vX.Y.Z-linux-aarch64.tar.gz (each with a .sha256; lib/, include/, the CMake package, LICENSE, NOTICE, VERSION), to its GitHub release and notifies the release hub, pineforge-release. The hub publishes the image, ghcr.io/pineforge-4pass/pineforge-release: this runtime, a pinned pineforge-codegen transpiler and the one-shot transpile + run harness of docker/, built from the release's static-lib tarball. The image is tagged with the hub's own version (X.Y.Z, X.Y, and latest for the newest stable one), with engine<E>-codegen<C> naming the pair it carries, and with sha-<short>; a release candidate gets no latest. Pin the engine<E>-codegen<C> tag of the engine release you build against: for v1.3.0, engine1.3.0-codegen1.3.0, the image the hub also tags 1.3.0.

docker pull ghcr.io/pineforge-4pass/pineforge-release:latest

Run the tutorial MACD strategy entirely inside the container; the image transpiles the .pine with its own codegen:

docker run --rm \
  -v "$(pwd)/tutorial/macd/strategy.pine:/in/strategy.pine:ro" \
  -v "$(pwd)/tutorial/data/btcusdt_15m_7d.csv:/in/ohlcv.csv:ro" \
  ghcr.io/pineforge-4pass/pineforge-release:latest > report.json

See docker/README.md for the full mount + JSON schema reference. This tree keeps that harness (docker/entrypoint.sh, docker/run_json.py) but no Dockerfile; the image's Dockerfile is pineforge-release's.

Verifying the install

A self-contained smoke test ships under cmake/smoke_consumer/:

cmake -S cmake/smoke_consumer -B build-smoke
cmake --build build-smoke
./build-smoke/smoke_version     # prints the runtime version string

If this prints the version you installed you're done: pf_version_string(), which is the VERSION file exactly (a release candidate's -rc.N included) for a tarball build or one configured with -DPINEFORGE_VERSION_SOURCE=FILE, and git describe's descriptor for a build from a git checkout. The program exits 1 instead if the CMake package's PineForge_VERSION_FULL, the installed pineforge/version.h and the linked library name different versions, or if its own multiply-add was fused; the configure step also checks that the package hands its consumers -ffp-contract=off.

Table of Contents