public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-gfx/openvdb/
Date: Sun, 20 Feb 2022 21:10:20 +0000 (UTC)	[thread overview]
Message-ID: <1645391400.c523e7434b40fd5c2ef22b41032d8e221f6ffef5.sam@gentoo> (raw)

commit:     c523e7434b40fd5c2ef22b41032d8e221f6ffef5
Author:     Bernd Waibel <waebbl-gentoo <AT> posteo <DOT> net>
AuthorDate: Fri Feb 18 13:23:46 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Feb 20 21:10:00 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c523e743

media-gfx/openvdb: enable CUDA support for NanoVDB

Also relaxes the dependency on tbb. We really only need >=tbb-2019.

Package-Manager: Portage-3.0.30, Repoman-3.0.3
Signed-off-by: Bernd Waibel <waebbl-gentoo <AT> posteo.net>
Closes: https://github.com/gentoo/gentoo/pull/24238
Signed-off-by: Sam James <sam <AT> gentoo.org>

 media-gfx/openvdb/metadata.xml                             |  3 +++
 .../{openvdb-9.0.0-r2.ebuild => openvdb-9.0.0-r3.ebuild}   | 14 +++++++++++---
 2 files changed, 14 insertions(+), 3 deletions(-)

diff --git a/media-gfx/openvdb/metadata.xml b/media-gfx/openvdb/metadata.xml
index abb456e35583..50b4f6e0bbd9 100644
--- a/media-gfx/openvdb/metadata.xml
+++ b/media-gfx/openvdb/metadata.xml
@@ -18,6 +18,9 @@
 		<flag name="blosc">
 			Allow using blosc compression via <pkg>dev-libs/c-blosc</pkg>
 		</flag>
+		<flag name="cuda">
+			Enable support for CUDA in NanoVDB.
+		</flag>
 		<flag name="nanovdb">
 			A lightweight, header only, and GPU friendly version of VDB.
 		</flag>

diff --git a/media-gfx/openvdb/openvdb-9.0.0-r2.ebuild b/media-gfx/openvdb/openvdb-9.0.0-r3.ebuild
similarity index 88%
rename from media-gfx/openvdb/openvdb-9.0.0-r2.ebuild
rename to media-gfx/openvdb/openvdb-9.0.0-r3.ebuild
index 1c94b6577b39..76343741a986 100644
--- a/media-gfx/openvdb/openvdb-9.0.0-r2.ebuild
+++ b/media-gfx/openvdb/openvdb-9.0.0-r3.ebuild
@@ -14,16 +14,17 @@ SRC_URI="https://github.com/AcademySoftwareFoundation/${PN}/archive/v${PV}.tar.g
 LICENSE="MPL-2.0"
 SLOT="0/9"
 KEYWORDS="~amd64 ~arm ~arm64 ~ppc64 ~x86"
-IUSE="cpu_flags_x86_avx cpu_flags_x86_sse4_2 +blosc doc +nanovdb numpy python static-libs test utils zlib abi6-compat abi7-compat abi8-compat +abi9-compat"
+IUSE="cpu_flags_x86_avx cpu_flags_x86_sse4_2 +blosc cuda doc +nanovdb numpy python static-libs test utils zlib abi6-compat abi7-compat abi8-compat +abi9-compat"
 RESTRICT="!test? ( test )"
 
 REQUIRED_USE="
 	numpy? ( python )
+	cuda? ( nanovdb )
 	^^ ( abi6-compat abi7-compat abi8-compat abi9-compat )
 	python? ( ${PYTHON_REQUIRED_USE} )
 "
 RDEPEND="
-	>=dev-cpp/tbb-2021.4.0:=
+	>=dev-cpp/tbb-2020.3:=
 	dev-libs/boost:=
 	dev-libs/jemalloc:=
 	dev-libs/log4cplus:=
@@ -37,6 +38,7 @@ RDEPEND="
 	x11-libs/libXinerama
 	x11-libs/libXrandr
 	blosc? ( dev-libs/c-blosc:= )
+	cuda? ( >=dev-util/nvidia-cuda-toolkit-11 )
 	python? (
 		${PYTHON_DEPS}
 		$(python_gen_cond_dep '
@@ -62,7 +64,6 @@ BDEPEND="
 "
 
 PATCHES=(
-	"${FILESDIR}/${PN}-7.1.0-0001-Fix-multilib-header-source.patch"
 	"${FILESDIR}/${PN}-8.1.0-glfw-libdir.patch"
 	"${FILESDIR}/${PN}-9.0.0-fix-atomic.patch"
 	"${FILESDIR}/${PN}-9.0.0-numpy.patch"
@@ -109,6 +110,13 @@ src_configure() {
 		-DUSE_NANOVDB=$(usex nanovdb)
 	)
 
+	if use nanovdb; then
+		mycmakeargs+=(
+			-DNANOVDB_BUILD_UNITTESTS=$(usex test)
+			-DNANOVDB_USE_CUDA=$(usex cuda)
+		)
+	fi
+
 	if use python; then
 		mycmakeargs+=(
 			-DOPENVDB_BUILD_PYTHON_MODULE=ON


             reply	other threads:[~2022-02-20 21:10 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-20 21:10 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-23 22:19 [gentoo-commits] repo/gentoo:master commit in: media-gfx/openvdb/ Conrad Kostecki
2024-05-28 17:01 Sam James
2024-04-13 17:36 Sam James
2024-04-05  1:21 Sam James
2024-02-20 13:42 Joonas Niilola
2023-02-01 18:38 Sam James
2023-02-01  5:15 Michał Górny
2022-09-29 19:58 Matthew Smith
2022-09-25  1:27 Sam James
2022-02-28  7:06 Yixun Lan
2022-02-28  5:21 Sam James
2022-02-23  2:20 Sam James
2022-02-23  2:19 Sam James
2022-02-20 21:10 Sam James
2022-02-20 21:10 Sam James
2022-02-18 22:48 Sam James
2022-02-16 19:28 Sam James
2021-12-04  1:10 Sam James
2021-10-31  8:42 Sam James
2021-10-31  8:40 Sam James
2021-10-31  8:38 Sam James
2021-10-31  8:38 Sam James
2021-10-31  7:17 Sam James
2021-10-31  5:53 Sam James
2021-10-31  2:21 Sam James
2021-10-31  2:20 Sam James
2021-10-31  2:20 Sam James
2021-10-31  2:19 Sam James
2021-10-31  2:19 Sam James
2021-10-31  2:19 Sam James
2021-10-31  2:19 Sam James
2021-10-30 17:25 Sam James
2021-10-29 22:23 Sam James
2021-10-26 11:13 Sam James
2021-06-10  0:51 Sam James
2021-03-05 18:39 Sam James
2021-02-22  7:12 Sam James
2021-01-25 14:16 Sam James
2020-12-21 18:07 Sam James
2020-11-08 10:29 Sam James
2020-10-15 15:58 Sam James
2020-08-25 18:06 Sam James
2020-08-25 18:03 Sam James
2020-08-24 13:42 Sam James
2020-08-24 13:42 Sam James
2020-08-24 13:42 Sam James
2020-08-24 13:42 Sam James
2020-08-24 13:42 Sam James
2020-08-24 13:42 Sam James
2020-08-24 13:42 Sam James
2020-08-24 13:42 Sam James
2020-08-24 13:42 Sam James
2020-08-24 13:42 Sam James
2020-08-24 13:42 Sam James
2020-03-01 18:36 Matthias Maier
2020-02-09 16:29 Michał Górny
2020-01-16  6:39 Michał Górny
2019-09-13 15:43 Michał Górny
2019-06-06 20:33 Andreas Sturmlechner
2019-05-25  8:52 Mikle Kolyada
2019-03-18 22:53 Patrice Clement
2018-08-14 11:39 Jonathan Scruggs
2018-08-07 17:05 Jonathan Scruggs
2018-03-30 16:04 Aaron Bauman
2018-01-27 17:19 Jonathan Scruggs
2017-09-23  8:38 David Seifert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1645391400.c523e7434b40fd5c2ef22b41032d8e221f6ffef5.sam@gentoo \
    --to=sam@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox