Skip to main content

Packaging

Wuwe produces a platform-specific SDK archive containing the library, public headers, CMake package files, examples, documentation, release metadata, and the default document-parsing runtime.

Build an archive​

Windows x64:

$env:VCPKG_ROOT = "D:\tools\vcpkg"
cmake --preset windows-vcpkg
cmake --build --preset windows-vcpkg-release
ctest --preset windows-vcpkg-release
.\tools\package-wuwe.ps1 -BuildDir build-vcpkg -Configuration Release

Linux x64:

export VCPKG_ROOT="$HOME/vcpkg"
cmake --preset linux-vcpkg
cmake --build --preset linux-vcpkg-release
ctest --preset linux-vcpkg-release
bash ./tools/package-wuwe.sh --build-dir build-linux-vcpkg --configuration Release

Windows produces a .zip; Linux produces a .tar.gz. Build each archive on its target operating system so native binaries, permissions, symbolic links, and the bundled JRE remain correct.

Archive contents​

  • public headers and static libraries
  • wuwe-config.cmake and exported CMake targets
  • docs and example source
  • README.md, LICENSE, VERSION, and vcpkg.json
  • manifest.json with resolved build and runtime capabilities
  • checksums.sha256
  • runtime/tika/tika-server-standard.jar
  • runtime/jre with the platform-specific Temurin 21 runtime

The packaging scripts use the pinned assets under third_party/runtime/ and verify their checksums. They do not download Tika or Java while packaging.

Install without creating an archive​

cmake --install build-vcpkg --config Release --prefix install

The install tree has the same SDK layout and, by default, the bundled runtime sidecars.

Default document runtime​

auto loader =
  wuwe::agent::knowledge::knowledge_document_loader::make_default();

The default loader registers local parsers, starts the bundled Tika server when the runtime is discoverable, and keeps that process alive for the loader lifetime. It uses runtime/jre/bin/java.exe on Windows and runtime/jre/bin/java on Linux.

What is not bundled​

The archive is a complete Wuwe SDK, not a copy of every C++ development package. A consumer of the static library must provide the public dependencies recorded by the build:

  • SQLite3 for SQLite-enabled packages;
  • OpenSSL for OpenSSL-enabled packages.

Use manifest.json and the exported CMake package as the source of truth for a specific archive.