[prev in list] [next in list] [prev in thread] [next in thread]
List: gentoo-dev
Subject: [gentoo-dev] New eclass: openvdb.eclass
From: Adrian Grigo <agrigo2001 () yahoo ! com ! au>
Date: 2020-05-27 1:40:04
Message-ID: 1055740577.138748.1590543604542 () mail ! yahoo ! com
[Download RAW message or body]
Hello, I am a proxied maintainer of blender and openvdb and wish to propose a new \
eclass and USE_EXPAND variable to ensure the same version of the openvdb abi is used \
when building the blender, openvdb and openimageio packages.
The tree currently contains openvdb 4 and 5, and I plan to add 6 and 7 soon to \
support my new blender PR. Each major release of openvdb has a new ABI, and can also \
support legacy versions. However only one version can be built at a time, which is \
passed to cmake through OPENVDB_ABI_VERSION_NUMBER, and produces a library with \
functions named xxx_7abi5 when building openvdb 7 with support for abi 5. Client \
packages like blender and openimageio which depend on openvdb and also need to be \
compiled with the same version number in order to link correctly.
To enforce this I propose to add a new USE_EXPAND variable called OPENVDB_ABI, which \
is set to the version number the user wants to use in the system eg 5, which expands \
to openvdb_abi_5. The packages can then append \
-DOPENVDB_ABI_VERSION_NUMBER=${OPENVDB_ABI} to ensure they pass the same value to \
cmake.
To reduce the boilerplate code required to ensure that only one supported value is \
set in OPENVDB_ABI and used by all packages, so I propose to add an eclass to \
maintain this in one place. Similar to PYTHON_COMPAT, each ebuilds set OPENVDB_COMPAT \
to specify which legacy ABI they can support. The openvdb.eclass uses it to set \
global variables OPENVDB_REQUIRED_USE and OPENVDB_SINGLE_USEDEP and verify in \
pkg_prepare that only one of the openvdb_abi_X flags is set.
Each ebuild sets REQUIRED_USE="${OPENVDB_REQUIRED_USE}" which evaluates to ^^ ( \
openvdb_abi_3 openvdb_abi_4 ... ) to ensure only one abi is enabled from those it \
supports. They set RDEPEND="openvdb? ( media-gfx/openvdb[${OPENVDB_SINGLE_USEDEP}] )" \
which evaluates to openvdb_abi_3(-)?,openvdb_abi_4(-)?,... to allow portage to \
enforce the same abi version is built between all packages.
With a new release of openvdb, I will only need to add it to the openvdb_abi.desc \
file, to an eclass internal list _OPENVDB_ALL_ABI, and to OPENVDB_COMPAT for each \
ebuild which supports the new version.
Please review my proposed eclass below. I have tested it works when OPENVDB_ABI is \
missing, set to invalid values, or set to values that cannot satisfy all package \
requirements simultaneously, and that the system recompiles all packages when the ABI \
is changed. It also works when set to appropriate values.
I considered other alternatives during development. It is possible to manually add \
the expanded REQUIRED_USE and RDEPEND strings to each package, but with each new \
version of openvdb and multiple client packages to maintain this becomes messy and \
error prone. The user also needs to set the same openvdb_abi_X flag for each package. \
While currently there are only three packages which need to be synchronised, any \
other package which depends on openvdb in future will benefit from this \
infrastructure.
Also without the USE_EXPAND variable the ebuilds do not have access to the version \
number to pass to the build system, and need to generate it by testing each USE flag. \
So I think this is the cleanest solution.
I also looked into slotting openvdb as then packages could specify the slot/subslot \
required eg openvdb:7/5 but don't think this is possible. This would be a major \
undertaking as it has a static as well as dynamic core library, another library for \
python, and the cmake modules that find openvdb use the output of a binary at \
/usr/bin/vdb_print to determine which version to link against. It would also not \
centralise the boilerplate code.
For further information and my discussion during development see \
https://github.com/redchillipadi/ebuild-overlay/issues/4
Please let me know if there is a better solution or improvements are required.
Kind Regards,
Adrian Grigo
# Copyright 1999-2020 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
# @ECLASS: openvdb.eclass
# @MAINTAINER:
# Adrian Grigo <agrigo2001@yahoo.com.au>
# @ AUTHOR:
# Author: Adrian Grigo <agrigo2001@yahoo.com.au>
# Based on work of: Michał Górny <mgorny@gentoo.org> and Krzysztof Pawlik \
<nelchael@gentoo.org> # @SUPPORTED_EAPIS: 5 6 7
# @BLURB: An eclass for OpenVDB to control which ABI version is compiled
# @DESCRIPTION:
# The OpenVDB package is a library for sorting and manipulating sparse
# data structures with dynamic topology as required for use in volume
# rendering for computer graphics.
#
# Each major version of OpenVDB provides an updated ABI, as well as
# the ability to compile using a legacy version of the ABI.
# Openvdb 7 can be compiled to support version 5, 6 or 7 of the ABI.
#
# However the user needs to choose at compile time which version to
# build by passing OPENVDB_ABI_VERSION_NUMBER="5" to cmake.
# It is not possible to support multiple versions concurrently
# so OpenVDB and all packages depending upon it must be built for the
# same ABI version. This currently means blender and openvdb, and
# will also include >=openimageio-2.0 once it is updated
#
# The client packages have differing requirements for the ABI support.
# For example,
# Openvdb-7 supports 5-7 (older version provide ABI 3 and 4 support)
# Blender supports ABI 4-7
# Openimageio-2.0 supports ABI 5-7.
#
# To use this eclass, the user should first select which ABI to build
# and set OPENVDB_ABI USE_EXPAND variable in make.conf.
#
# When the client package inherits this eclass, it can use the
# OPENVDB_COMPAT variable in the ebuild to specify which ABI it
# supports, and then use the OPENVDB_SINGLE_USEDEP variable that the
# eclass produces to force the package to link using ABI selected in
# OPENVDB_ABI
# eg. openvdb? ( media-gfx/openvdb[${OPENVDB_SINGLE_USEDEP}] )
# When OPENVDB_COMPAT="X Y" the variable evaluates to
# openvdb_abi_X(-)? openvdb_abi_Y(-)?
#
# The client can pass the ABI version to the build system as follows:
# append-cppflags -DOPENVDB_ABI_VERSION_NUMBER="${OPENVDB_ABI}"
#
# This eclass includes pkg_setup which ensures that the package will
# only compile if only one openvdb_abi_X USE flag is set
#
# @EXAMPLE:
# The user needs to choose which version of the ABI supports all packages
# they plan to install. This is then stored in a variable in make.conf
# eg. OPENVDB_ABI="5" in /etc/portage/make.conf
#
# The client packages need to:
# - inherit this eclass.
# - list the ABI supported by the package in OPENVDB_COMPAT.
# - use OPENVDB_REQUIRED_USE to ensure that only one of the
# compatible ABI can be selected by the ebuild.
# - include OPENVDB_SINGLE_USEDEP in RDEPEND to ensure any
# dependencies build against a similar ABI.
# - pass the OPENVDB_ABI version to the package build system
#
# @CODE
# inherit openvdb
# OPENVDB_COMPAT=( 4 5 6 7 )
# REQUIRED_USE="openvdb? ( ${OPENVDB_REQUIRED_USE} )"
# RDEPEND="openvdb? ( media-gfx/openvdb[${OPENVDB_SINGLE_USEDEP}] )"
#
# src_configure() {
# append-cppflags -DOPENVDB_ABI_VERSION_NUMBER="${OPENVDB_ABI_VERSION}"
# ...
# cmake-utils_src_configure
# }
# @CODE
case "${EAPI:-0}" in
0|1|2|3|4)
die "Unsupported EAPI=${EAPI:-0} (too old) for ${ECLASS}"
;;
5|6|7)
# EAPI=5 is required for sane USE_EXPAND dependencies
;;
*)
die "Unsupported EAPI=${EAPI} (unknown) for ${ECLASS}"
;;
esac
EXPORT_FUNCTIONS pkg_setup
# @ECLASS-VARIABLE: OPENVDB_COMPAT
# @REQUIRED
# @DESCRIPTION:
# This variable contains a list of OpenVDB ABI the package supports.
# It must be set before the 'inherit' call and has to be an array.
#
# Example use:
# @CODE
# OPENVDB_COMPAT=( 4 5 6 7 )
# @CODE
#
# @ECLASS-VARIABLE: OPENVDB_SINGLE_USEDEP
# @DESCRIPTION:
# This is an eclass generated USE-dependency flag which can be used by
# any package depending on openvdb to ensure the correct ABI version
# support is built.
#
# Example use:
# @CODE
# RDEPEND="openvdb? ( media-gfx/openvdb[${OPENVDB_SINGLE_USEDEP}] )"
# @CODE
#
# Example value:
# @CODE
# openvdb_abi_3(-)?,openvdb_abi_4(-)?,openvdb_abi_5(-)?...
# @CODE
# @ECLASS-VARIABLE: OPENVDB_REQUIRED_USE
# @DESCRIPTION:
# This is an eclass-generated required use expression which ensures
# that exactly one openvdb_use_X value has been enabled.
#
# Example use:
# @CODE
# REQUIRED_USE="${OPENVDB_REQUIRED_USE}"
# @CODE
#
# Example value:
# @CODE
# ^^ ( openvdb_abi_3 openvdb_abi_4 openvdb_abi_5 openvdb_abi_6 openvdb_abi_7)
# @CODE
# @ECLASS-VARIABLE: _OPENVDB_ALL_ABI
# @INTERNAL
# @DESCRIPTION:
# All supported OpenVDB ABI
# Update this with each new major version release of OpenVDB
_OPENVDB_ALL_ABI=(
3 4 5 6 7
)
readonly _OPENVDB_ALL_ABI
# @FUNCTION: _openvdb_set_globals
# @INTERNAL
# @DESCRIPTION:
# Ensure that OPENVDB_COMPAT is valid and generate the
# OPENVDB_REQUIRED_USE and OPENVDB_SINGLE_USEDEP global variables for
# use by the inheriting ebuild
_openvdb_set_globals() {
local i
if ! declare -p OPENVDB_COMPAT &>/dev/null; then
die 'OPENVDB_COMPAT not declared.'
fi
if [[ $(declare -p OPENVDB_COMPAT) != "declare -a"* ]]; then
die 'OPENVDB_COMPAT must be an array.'
fi
local flags=()
for i in "${_OPENVDB_ALL_ABI[@]}"; do
if has "${i}" "${OPENVDB_COMPAT[@]}"; then
flags+=( "openvdb_abi_${i}" )
fi
done
if [[ ${#supp[@]} -eq 1 ]]; then
IUSE="+${flags[0]}"
else
IUSE="${flags[*]}"
fi
if [[ ! ${#flags[@]} ]]; then
die "No supported OpenVDB ABI in OPENVDB_COMPAT."
fi
local single_flags="${flags[@]/%/(-)?}"
local single_usedep=${single_flags// /,}
OPENVDB_REQUIRED_USE="^^ ( ${flags[*]} )"
OPENVDB_SINGLE_USEDEP="${single_usedep}"
readonly OPENVDB_REQUIRED_USE OPENVDB_SINGLE_USEDEP
}
_openvdb_set_globals
unset -f _openvdb_set_globals
if [[ ! ${_OPENVDB} ]]; then
# @FUNCTION: openvdb_setup
# @DESCRIPTION
# Ensure one and only one OpenVDB ABI version is selected
openvdb_setup() {
debug-print-function ${FUNCNAME} "${@}"
local i, version
for i in "${_OPENVDB_ABI[@]}"; do
if use "openvdb_abi_${i}"; then
if [[ ${version} ]]; then
eerror "Your OPENVDB_ABI setting lists more than a single \
OpenVDB"
eerror "ABI version. Please set it to just one value."
echo
die "More than one ABI in OPENVDB_ABI."
fi
fi
version="${i}"
echo "Using OpenVDB ABI ${version} to build"
done
if [[ ! ${version} ]]; then
eerror "No OpenVDB ABI Version selected for the system. Please set"
eerror "the OPENVDB_ABI variable in your make.conf to one"
eerror "of the values contained in all of:"
eerror
eerror "- the entire list of ABI: ${_OPENVDB_ALL_ABI[*]}"
eerror "- the ABI supported by this package: ${OPENVDB_COMPAT}"
eerror "- and the ABI supported by all other packages on your system"
echo
die "No supported OpenVDB ABI version in OPENVDB_ABI."
fi
}
# @FUNCTION: openvdb_pkg_setup
# @DESCRIPTION:
# Runs openvdb_setup.
openvdb_pkg_setup() {
debug-print-function ${FUNCNAME} "${@}"
[[ ${MERGE_TYPE} != binary ]] && openvdb_setup
}
_OPENVDB=1
fi
[Attachment #3 (text/html)]
<html><head></head><body><div class="yahoo-style-wrap" style="font-family:Helvetica \
Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div dir="ltr" \
data-setdir="false"><div>Hello, I am a proxied maintainer of blender and openvdb and \
wish to propose a new eclass and USE_EXPAND variable to ensure the same version of \
the openvdb abi is used when building the blender, openvdb and openimageio \
packages.<br><br>The tree currently contains openvdb 4 and 5, and I plan to add 6 and \
7 soon to support my new blender PR. Each major release of openvdb has a new ABI, and \
can also support legacy versions. However only one version can be built at a time, \
which is passed to cmake through OPENVDB_ABI_VERSION_NUMBER, and produces a library \
with functions named xxx_7abi5 when building openvdb 7 with support for abi 5. Client \
packages like blender and openimageio which depend on openvdb and also need to be \
compiled with the same version number in order to link correctly.<br><br>To enforce \
this I propose to add a new USE_EXPAND variable called OPENVDB_ABI, which is set to \
the version number the user wants to use in the system eg 5, which expands to \
openvdb_abi_5. The packages can then append \
-DOPENVDB_ABI_VERSION_NUMBER=${OPENVDB_ABI} to ensure they pass the same value to \
cmake.<br><br>To reduce the boilerplate code required to ensure that only one \
supported value is set in OPENVDB_ABI and used by all packages, so I propose to add \
an eclass to maintain this in one place. Similar to PYTHON_COMPAT, each ebuilds set \
OPENVDB_COMPAT to specify which legacy ABI they can support. The openvdb.eclass uses \
it to set global variables OPENVDB_REQUIRED_USE and OPENVDB_SINGLE_USEDEP and verify \
in pkg_prepare that only one of the openvdb_abi_X flags is set.<br><br>Each ebuild \
sets REQUIRED_USE="${OPENVDB_REQUIRED_USE}" which evaluates to ^^ ( openvdb_abi_3 \
openvdb_abi_4 ... ) to ensure only one abi is enabled from those it supports.<br>They \
set RDEPEND="openvdb? ( media-gfx/openvdb[${OPENVDB_SINGLE_USEDEP}] )" which \
evaluates to openvdb_abi_3(-)?,openvdb_abi_4(-)?,... to allow portage to enforce the \
same abi version is built between all packages.<br><br>With a new release of openvdb, \
I will only need to add it to the openvdb_abi.desc file, to an eclass internal list \
_OPENVDB_ALL_ABI, and to OPENVDB_COMPAT for each ebuild which supports the new \
version.<br><br>Please review my proposed eclass below. I have tested it works when \
OPENVDB_ABI is missing, set to invalid values, or set to values that cannot satisfy \
all package requirements simultaneously, and that the system recompiles all packages \
when the ABI is changed. It also works when set to appropriate values.<br><br>I \
considered other alternatives during development. It is possible to manually add the \
expanded REQUIRED_USE and RDEPEND strings to each package, but with each new version \
of openvdb and multiple client packages to maintain this becomes messy and error \
prone. The user also needs to set the same openvdb_abi_X flag for each package. While \
currently there are only three packages which need to be synchronised, any other \
package which depends on openvdb in future will benefit from this \
infrastructure.<br><br>Also without the USE_EXPAND variable the ebuilds do not have \
access to the version number to pass to the build system, and need to generate it by \
testing each USE flag. So I think this is the cleanest solution.<br><br>I also looked \
into slotting openvdb as then packages could specify the slot/subslot required eg \
openvdb:7/5 but don't think this is possible. This would be a major undertaking as it \
has a static as well as dynamic core library, another library for python, and the \
cmake modules that find openvdb use the output of a binary at /usr/bin/vdb_print to \
determine which version to link against. It would also not centralise the boilerplate \
code.<br><br>For further information and my discussion during development see \
https://github.com/redchillipadi/ebuild-overlay/issues/4<br><br>Please let me know if \
there is a better solution or improvements are required.<br><br>Kind \
Regards,<br>Adrian Grigo<br><br><br># Copyright 1999-2020 Gentoo Authors<br># \
Distributed under the terms of the GNU General Public License v2<br><br># @ECLASS: \
openvdb.eclass<br># @MAINTAINER:<br># Adrian Grigo \
<agrigo2001@yahoo.com.au><br># @ AUTHOR:<br># Author: Adrian Grigo \
<agrigo2001@yahoo.com.au><br># Based on work of: Michał Górny \
<mgorny@gentoo.org> and Krzysztof Pawlik <nelchael@gentoo.org><br># \
@SUPPORTED_EAPIS: 5 6 7<br># @BLURB: An eclass for OpenVDB to control which ABI \
version is compiled<br># @DESCRIPTION:<br># The OpenVDB package is a library for \
sorting and manipulating sparse<br># data structures with dynamic topology as \
required for use in volume<br># rendering for computer graphics.<br>#<br># Each major \
version of OpenVDB provides an updated ABI, as well as<br># the ability to compile \
using a legacy version of the ABI.<br># Openvdb 7 can be compiled to support version \
5, 6 or 7 of the ABI.<br>#<br># However the user needs to choose at compile time \
which version to<br># build by passing OPENVDB_ABI_VERSION_NUMBER="5" to cmake.<br># \
It is not possible to support multiple versions concurrently<br># so OpenVDB and all \
packages depending upon it must be built for the<br># same ABI version. This \
currently means blender and openvdb, and<br># will also include >=openimageio-2.0 \
once it is updated<br>#<br># The client packages have differing requirements for the \
ABI support.<br># For example,<br># Openvdb-7 supports 5-7 (older version provide ABI \
3 and 4 support)<br># Blender supports ABI 4-7<br># Openimageio-2.0 supports ABI \
5-7.<br>#<br># To use this eclass, the user should first select which ABI to \
build<br># and set OPENVDB_ABI USE_EXPAND variable in make.conf.<br>#<br># When the \
client package inherits this eclass, it can use the<br># OPENVDB_COMPAT variable in \
the ebuild to specify which ABI it<br># supports, and then use the \
OPENVDB_SINGLE_USEDEP variable that the<br># eclass produces to force the package to \
link using ABI selected in<br># OPENVDB_ABI<br># eg. openvdb? ( \
media-gfx/openvdb[${OPENVDB_SINGLE_USEDEP}] )<br># When OPENVDB_COMPAT="X Y" the \
variable evaluates to<br># openvdb_abi_X(-)? openvdb_abi_Y(-)?<br>#<br># The client \
can pass the ABI version to the build system as follows:<br># append-cppflags \
-DOPENVDB_ABI_VERSION_NUMBER="${OPENVDB_ABI}"<br>#<br># This eclass includes \
pkg_setup which ensures that the package will<br># only compile if only one \
openvdb_abi_X USE flag is set<br>#<br># @EXAMPLE:<br># The user needs to choose which \
version of the ABI supports all packages<br># they plan to install. This is then \
stored in a variable in make.conf<br># eg. OPENVDB_ABI="5" in \
/etc/portage/make.conf<br>#<br># The client packages need to:<br># - inherit this \
eclass.<br># - list the ABI supported by the package in OPENVDB_COMPAT.<br># - use \
OPENVDB_REQUIRED_USE to ensure that only one of the<br># compatible ABI \
can be selected by the ebuild.<br># - include OPENVDB_SINGLE_USEDEP in RDEPEND to \
ensure any<br># dependencies build against a similar ABI.<br># - pass the \
OPENVDB_ABI version to the package build system<br>#<br># @CODE<br># inherit \
openvdb<br># OPENVDB_COMPAT=( 4 5 6 7 )<br># REQUIRED_USE="openvdb? ( \
${OPENVDB_REQUIRED_USE} )"<br># RDEPEND="openvdb? ( \
media-gfx/openvdb[${OPENVDB_SINGLE_USEDEP}] )"<br>#<br># src_configure() \
{<br># append-cppflags \
-DOPENVDB_ABI_VERSION_NUMBER="${OPENVDB_ABI_VERSION}"<br># \
...<br># cmake-utils_src_configure<br># }<br># @CODE<br><br>case \
"${EAPI:-0}" in<br> 0|1|2|3|4)<br> \
die "Unsupported EAPI=${EAPI:-0} (too old) for ${ECLASS}"<br> \
;;<br> 5|6|7)<br> \
# EAPI=5 is required for sane USE_EXPAND \
dependencies<br> ;;<br> \
*)<br> die "Unsupported EAPI=${EAPI} \
(unknown) for ${ECLASS}"<br> \
;;<br>esac<br><br>EXPORT_FUNCTIONS pkg_setup<br><br># @ECLASS-VARIABLE: \
OPENVDB_COMPAT<br># @REQUIRED<br># @DESCRIPTION:<br># This variable contains a list \
of OpenVDB ABI the package supports.<br># It must be set before the 'inherit' call \
and has to be an array.<br>#<br># Example use:<br># @CODE<br># OPENVDB_COMPAT=( 4 5 6 \
7 )<br># @CODE<br>#<br><br># @ECLASS-VARIABLE: OPENVDB_SINGLE_USEDEP<br># \
@DESCRIPTION:<br># This is an eclass generated USE-dependency flag which can be used \
by<br># any package depending on openvdb to ensure the correct ABI version<br># \
support is built.<br>#<br># Example use:<br># @CODE<br># RDEPEND="openvdb? ( \
media-gfx/openvdb[${OPENVDB_SINGLE_USEDEP}] )"<br># @CODE<br>#<br># Example \
value:<br># @CODE<br># openvdb_abi_3(-)?,openvdb_abi_4(-)?,openvdb_abi_5(-)?...<br># \
@CODE<br><br># @ECLASS-VARIABLE: OPENVDB_REQUIRED_USE<br># @DESCRIPTION:<br># This is \
an eclass-generated required use expression which ensures<br># that exactly one \
openvdb_use_X value has been enabled.<br>#<br># Example use:<br># @CODE<br># \
REQUIRED_USE="${OPENVDB_REQUIRED_USE}"<br># @CODE<br>#<br># Example value:<br># \
@CODE<br># ^^ ( openvdb_abi_3 openvdb_abi_4 openvdb_abi_5 openvdb_abi_6 \
openvdb_abi_7)<br># @CODE<br><br># @ECLASS-VARIABLE: _OPENVDB_ALL_ABI<br># \
@INTERNAL<br># @DESCRIPTION:<br># All supported OpenVDB ABI<br># Update this with \
each new major version release of OpenVDB<br>_OPENVDB_ALL_ABI=(<br> \
3 4 5 6 7<br>)<br>readonly _OPENVDB_ALL_ABI<br><br># @FUNCTION: \
_openvdb_set_globals<br># @INTERNAL<br># @DESCRIPTION:<br># Ensure that \
OPENVDB_COMPAT is valid and generate the<br># OPENVDB_REQUIRED_USE and \
OPENVDB_SINGLE_USEDEP global variables for<br># use by the inheriting \
ebuild<br>_openvdb_set_globals() {<br> local i<br><br> \
if ! declare -p OPENVDB_COMPAT &>/dev/null; then<br> \
die 'OPENVDB_COMPAT not declared.'<br> \
fi<br><br> if [[ $(declare -p OPENVDB_COMPAT) != "declare \
-a"* ]]; then<br> die 'OPENVDB_COMPAT must be an \
array.'<br> fi<br><br> local \
flags=()<br> for i in \
"${_OPENVDB_ALL_ABI[@]}"; do<br> if has "${i}" \
"${OPENVDB_COMPAT[@]}"; then<br> \
flags+=( "openvdb_abi_${i}" )<br> \
fi<br> done<br><br> \
if [[ ${#supp[@]} -eq 1 ]]; then<br> \
IUSE="+${flags[0]}"<br> else<br> \
IUSE="${flags[*]}"<br> \
fi<br><br> if [[ ! ${#flags[@]} ]]; then<br> \
die "No supported OpenVDB ABI in \
OPENVDB_COMPAT."<br> fi<br><br> local \
single_flags="${flags[@]/%/(-)?}"<br> local \
single_usedep=${single_flags// /,}<br><br> OPENVDB_REQUIRED_USE="^^ \
( ${flags[*]} )"<br> \
OPENVDB_SINGLE_USEDEP="${single_usedep}"<br> readonly \
OPENVDB_REQUIRED_USE OPENVDB_SINGLE_USEDEP<br>}<br>_openvdb_set_globals<br>unset -f \
_openvdb_set_globals<br><br>if [[ ! ${_OPENVDB} ]]; then<br><br># @FUNCTION: \
openvdb_setup<br># @DESCRIPTION<br># Ensure one and only one OpenVDB ABI version is \
selected<br>openvdb_setup() {<br> debug-print-function ${FUNCNAME} \
"${@}"<br><br> local i, version<br> for i in \
"${_OPENVDB_ABI[@]}"; do<br> if use \
"openvdb_abi_${i}"; then<br> \
if [[ ${version} ]]; then<br> \
eerror "Your OPENVDB_ABI setting lists more than a single \
OpenVDB"<br> \
eerror "ABI version. Please set it to just one value."<br> \
echo<br> \
die "More than one ABI \
in OPENVDB_ABI."<br> \
fi<br> fi<br><br> \
version="${i}"<br> echo \
"Using OpenVDB ABI ${version} to build"<br> \
done<br><br> if [[ ! ${version} ]]; then<br> \
eerror "No OpenVDB ABI Version selected for the system. \
Please set"<br> eerror "the OPENVDB_ABI variable \
in your make.conf to one"<br> eerror "of the \
values contained in all of:"<br> \
eerror<br> eerror "- the entire list of \
ABI: ${_OPENVDB_ALL_ABI[*]}"<br> eerror "- the \
ABI supported by this package: ${OPENVDB_COMPAT}"<br> \
eerror "- and the ABI supported by all other packages on your \
system"<br> echo<br> \
die "No supported OpenVDB ABI version in \
OPENVDB_ABI."<br> fi<br>}<br><br># @FUNCTION: \
openvdb_pkg_setup<br># @DESCRIPTION:<br># Runs openvdb_setup.<br>openvdb_pkg_setup() \
{<br> debug-print-function ${FUNCNAME} "${@}"<br><br> \
[[ ${MERGE_TYPE} != binary ]] && \
openvdb_setup<br>}<br><br>_OPENVDB=1<br>fi<br><br></div><div><br></div></div></div></body></html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic