Skip to content

Holoscan install source vs Holoscan module lifecycle

Holoscan install source is an open-source agent skill for developer tools. Holoscan module lifecycle is an open-source agent skill for developer tools.

  • Holoscan install source is best for build holoscan sdk 5.x from a specific development branch.
  • Holoscan module lifecycle is best for scaffold a new reusable holoscan operator module in its own repository.
What it is
Holoscan install source is an open-source agent skill for developer tools.
Holoscan module lifecycle is an open-source agent skill for developer tools.
Best for
Build Holoscan SDK 5.x from a specific development branch
Scaffold a new reusable Holoscan operator module in its own repository
Kind
Skill
Skill
Pricing
Open source
Open source
Platforms
Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, Goose
Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, Goose
GitHub stars
4K
4K
Last commit
Nov 2026
Nov 2026
License
Apache-2.0
Apache-2.0
Open source
Good for
Build Holoscan SDK 5.x from a specific development branch; Verify a local Holoscan SDK checkout matches a requested commit before building; Configure a debug or ARM64 build of the Holoscan SDK
Scaffold a new reusable Holoscan operator module in its own repository; Add Python bindings to an existing C++ Holoscan module; Build and test a Holoscan module with the Holoscan CLI

What Holoscan install source does

  • Source ref validation

    Resolves the requested 5.x tag or branch to a commit and compares it with the existing checkout before building.

  • Prerequisite checks

    Checks Linux, disk space, GPU driver, Git, Docker, buildx and the NVIDIA Container Toolkit before starting.

  • Build wrapper workflow

    Uses the repository run wrapper to check dependencies, dry-run and build the SDK with configurable options.

  • Build option guidance

    Explains debug and release types, ARM64 targets, custom paths, C++-only builds and optional component toggles.

  • Test verification

    Runs selected CTest cases for C++ and Python pipelines and requires that tests were actually executed.

  • Consumer integration notes

    Shows how to set CMAKE_PREFIX_PATH to the install prefix so downstream projects can find the SDK.

What Holoscan module lifecycle does

  • Module layout and naming

    Sets up a standalone holoscan-named repository with consistent display, module, package and operator names.

  • Template scaffolding

    Generates a new module with the packaged Holoscan CLI template, with C++ and optional Python bindings.

  • Producer and consumer tests

    Adds deterministic tests and a small demo that uses the module through its public surface.

  • Clean consumer verification

    Checks that installed packages work from an artifact-only consumer, including CMake and Python imports.

  • DEB and WHEEL packaging

    Builds and inspects package artifacts, including the declared Holoscan dependency for DEB builds.

  • Safe cleanup and approvals

    Removes task-owned install prefixes and avoids commits, publishing or privilege changes without authorization.

Holoscan install source vs Holoscan module lifecycle: questions

Is Holoscan install source or Holoscan module lifecycle cheaper?

Both are open source. Compare current plans on each official site.

What is the difference between Holoscan install source and Holoscan module lifecycle?

Holoscan install source is an open-source agent skill for developer tools. Holoscan module lifecycle is an open-source agent skill for developer tools.

Keep comparing