vipm-io/VIPM Build

Build a VI Package (.vip) with VIPM inside a LabVIEW Linux container

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
pathPath to the build specification to build: a .vipb file, a .lvproj file, or a directory containing exactly one .vipb (or one .lvproj). Resolved relative to working_directory.yes
working_directoryDirectory to resolve paths from and run VIPM in.no.
labview_versionLabVIEW version to build with. Optional: when empty, the highest LabVIEW installed in the container is used. Accepts a year (e.g. "2020", "2026") or a LabVIEW version number (e.g. "20.0", "24.1"). The value is validated against the LabVIEW versions actually installed in the container.no""
labview_bitnessLabVIEW bitness: 32 or 64.no64
version_numberOverride the package version (1-4 components, e.g. 1.2.3.4) -> --version-number.no""
build_numberOverride the build number (4th version component) -> --build-number.no""
debugBuild in debug mode (preserves block diagrams / front panels) -> --debug.nofalse
no_depsSkip building dependencies -> --no-deps.nofalse
rebuild_depsForce rebuild of all dependencies -> --rebuild-deps.nofalse
allow_package_driftAllow builds when installed packages disagree with the manifest -> --allow-package-drift.nofalse
lvproj_build_specName of the build spec within a .lvproj -> --lvproj-build-spec.no""
lvproj_targetTarget within the .lvproj to scope the build spec lookup -> --lvproj-target.no""
timeoutMaximum build time in seconds -> --timeout.no""
show_progressForce the progress bar on -> --show-progress.nofalse
verboseShow additional per-operation detail -> --verbose.notrue
extra_argsAdditional raw arguments appended verbatim to `vipm build` (word-split).no""
refreshRun `vipm refresh` before building (true/false).nofalse
refresh_argsAdditional raw arguments for `vipm refresh` (e.g. --no-cache, --force).no""
installDependencies to install before building, as a comma-delimited or newline-delimited list. Each entry may be a .vipc, .dragon, .vip, .ogp file, or a package name. Each entry is installed with its own `vipm install` invocation.no""
install_argsAdditional raw arguments applied to every `vipm install` (e.g. --upgrade).no""
output_directoryIf set, built .vip file(s) are copied into this directory.no""
install_vipmWhen to install VIPM: auto (install only if missing), always, or never.noauto
vipm_release_typeVIPM release channel to install from: develop, preview, or stable.nostable
vipm_versionVIPM version to install: "latest" (latest on the selected channel), a channel alias like "latest_preview", or an exact version (e.g. 25.3.3042).nolatest
vipm_cliExplicit path to the VIPM CLI. When empty, it is auto-detected.no""
community_editionBuild with VIPM Community Edition (exports VIPM_COMMUNITY_EDITION=true). Set to false for VIPM Pro.notrue
namedescription
vip_pathPath to the primary built .vip file (empty if none was produced).
vip_pathsNewline-delimited list of all .vip files produced by the build.
labview_versionThe LabVIEW version (year) actually used for the build.
vipm_versionThe version of the VIPM CLI used.
statusBuild status: success or failed.