brew

openvdb mit Homebrew, apk, dnf, MacPorts, Nix, pacman, apt, zypper installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für openvdb in AI-Agent-Workflows.

Installationsbefehl Sicherheitshinweise

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%

brew install openvdb

local Homebrew formula metadata

MacPortsverifiziert · 94%

sudo port install openvdb

MacPorts ports tree · graphics/openvdb/Portfile · Quelle: api.github.com

Linux

Alpine Linux apkverifiziert · 92%

sudo apk add openvdb

Alpine Linux edge package indexes · openvdb · Quelle: dl-cdn.alpinelinux.org

Fedora dnfverifiziert · 92%

sudo dnf install openvdb

Fedora Rawhide package metadata · openvdb · Quelle: dl.fedoraproject.org

Nixverifiziert · 92%

nix profile install nixpkgs#openvdb

nixpkgs package indexes · pkgs/by-name/op/openvdb/package.nix · Quelle: api.github.com

Arch Linux pacmanverifiziert · 92%

sudo pacman -S openvdb

Arch Linux sync databases · openvdb · Quelle: geo.mirror.pkgbuild.com

Debian aptverifiziert · 92%

sudo apt install libnanovdb-dev

Debian stable package indexes · libnanovdb-dev · Quelle: deb.debian.org

openSUSE zypperverifiziert · 92%

sudo zypper install libopenvdb13_0

openSUSE Tumbleweed package metadata · libopenvdb13_0 · Quelle: download.opensuse.org

Überblick

Paketzusammenfassung

Sparse volumetric data processing toolkit

Projektlinks

Befehle und Aliase

nanovdb_print
nanovdb_validate
vdb_print

Verlauf

Projektgeschichte und Nutzung

OpenVDB is an Academy Award-winning C++ library and file format for sparse volumetric data: fog, smoke, clouds, water simulations, level sets, particles, and other 3D grids where most voxels are empty. It began inside DreamWorks Animation and became one of the visual-effects world's standard volume interchange and processing packages.

Projektgeschichte

OpenVDB was developed at DreamWorks Animation, with the project site naming Ken Museth, Peter Cucka, Mihai Alden, and David Hill as primary original developers. DreamWorks released it to the open source community in August 2012 after using the underlying sparse-volume technology in feature-film production.

The original emphasis was efficient level-set storage and manipulation, but the public library expanded into a broader volume toolkit: tree-based sparse grids, file I/O, filtering, meshing, topology operations, Python bindings, and command-line inspection tools. NanoVDB later extended the ecosystem with a compact, GPU-friendly representation for read-only sparse volumes.

In October 2018 the Academy Software Foundation accepted OpenVDB as its first hosted project, moving governance from a studio-maintained open source release toward a neutral foundation home for film and animation infrastructure.

Adoptionsgeschichte

OpenVDB spread because it solved a production problem shared by many studios: dense 3D volumes are expensive to store, move, and render, while effects work often touches only a sparse subset of space. ASWF described it as an industry-standard technology for more detailed volumetric imagery such as water, clouds, ice, and liquid simulations.

The package became a common dependency in digital-content-creation and rendering stacks because tools can exchange volumes through VDB files instead of inventing private cache formats. The ASWF announcement cites adoption for feature-film effects at DreamWorks, and the project appears in package managers as both a development library and a set of utilities such as vdb_print and NanoVDB validators.

Wie es verwendet wird

Developers and technical directors use OpenVDB to create, read, transform, filter, combine, resample, and serialize sparse volumes. In package-manager form it is usually installed as a native library for DCC applications, renderers, simulation tools, converters, and pipeline scripts rather than as a standalone end-user application.

The command-line tools matter for pipeline debugging: package users can inspect VDB metadata and validate NanoVDB data without launching a full DCC program.

Warum Paket-Nerds sich dafür interessieren

OpenVDB is a package-nerd classic because a specialized movie-studio data structure escaped into the general open source supply chain. It brings heavy C++ dependencies, ABI concerns, Python bindings, file-format compatibility, and graphics-pipeline expectations into ordinary distro and Homebrew packaging.

It also shows how VFX infrastructure packages mature: studio origin, open source release, broad toolchain adoption, and foundation governance under ASWF alongside projects such as OpenColorIO, OpenEXR, OpenTimelineIO, and Open Shading Language.

Zeitleiste

2012-08-03: DreamWorks Animation announces the open source release of OpenVDB.
2018-10-23: ASWF announces OpenVDB as its first hosted project.
2020: NanoVDB is introduced as a compact GPU-oriented companion representation within the OpenVDB ecosystem.
2024: OpenVDB 12.0 relicenses the project from MPL-2.0 to Apache-2.0 after approval from major copyright holders.

Related projects

OpenVDB is closely related to NanoVDB, Houdini-style volume workflows, renderers and simulation systems that consume VDB caches, ASWF infrastructure projects such as OpenEXR and OpenColorIO, and DCC applications that need a shared sparse-volume interchange format.

Quellen

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

narrow executable package without higher-risk signals

Signale

metadata:no-higher-risk-signals

Installationsverhalten

In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
Installiert mit 5 Laufzeitabhängigkeiten.
Build-Metadaten listen 2 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

Befehl	Art	Sichtbarkeit
`nanovdb_print`	cli	globales Executable
`nanovdb_validate`	cli	globales Executable
`vdb_print`	cli	globales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-10

Manager-Version13.0.0

Manager aktualisiert

lokale DatenOK

Upstreamaktuell

neueste erkannte Versionv13.0.0

https://github.com/AcademySoftwareFoundation/openvdb

InfoNo package-manager update timestamp was available.niedrig Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüssel	brew:openvdb
Version	13.0.0
Paketmanager	Homebrew
Paketmanager-Seite	https://formulae.brew.sh/formula/openvdb
Homepage	https://www.openvdb.org/
Repository	https://github.com/AcademySoftwareFoundation/openvdb
Upstream-Dokumentation	https://www.openvdb.org/documentation
Lizenz	MPL-2.0
Quellarchiv	https://github.com/AcademySoftwareFoundation/openvdb/archive/refs/tags/v13.0.0.tar.gz
Abhängigkeiten	boost, c-blosc, jemalloc, openexr, tbb
Build-Abhängigkeiten	cmake, doxygen
Bottle	verfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install	nicht definiert
Dienst	keiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	openvdb
Version Scheme	0
Revision	1
Head Version	HEAD
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	head stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Debian apt95%

libnanovdb-dev 10.0.1-2.3+b1

Sparse Volume Processing toolkit - NanoVDB - dev