Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#62037 - [openimageio] 1.8.17-2 - python broken
Attached to Project:
Community Packages
Opened by Samuel Nicholas (enetheru) - Sunday, 17 March 2019, 03:53 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Wednesday, 27 March 2019, 22:23 GMT
Opened by Samuel Nicholas (enetheru) - Sunday, 17 March 2019, 03:53 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Wednesday, 27 March 2019, 22:23 GMT
|
DetailsDescription: As stated in the PKGBUILD python3 bindings are not built / do not work.
As i need it for myself i looked into the PKGBUILD and found that the package is outdated, but also that the build steps are somewhat strange. The openimageio source has a top level makefile which facilitates the cmake process and is very informative in terms of what options are valid for a build. There is no facility to concurrently build python 2 and python3 bindings, other maintainers have stated that they build twice, I only needed python 3. I have attached my PKGBUILD in hopes it will help, I use the latest version of openimageio. I would be delighted to be mentored in updating the PKGBUILD so that it is as robust as possible if anyone has the time. This is my first time submitting a bug/feature request, so if i messed anything up let me know. 
PKGBUILD
(1.4 KiB)
|
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Wednesday, 27 March 2019, 22:23 GMT
Reason for closing: Fixed
Wednesday, 27 March 2019, 22:23 GMT
Reason for closing: Fixed
oiio-1.8.17/pkg/openimageio/usr/lib/python2.7
the problem is your cmake defines are misinformed, from the build itself:
Manually-specified variables were not used by the project:
PYLIB3_INSTALL_DIR
USE_PYTHON3
try instead using what is used in their own makefile:
-DPYTHON_VERSION:STRING=3.7.2 \
earliest reference to this is from 2011: https://github.com/OpenImageIO/oiio/issues/197
I don't know where you got the initial cmake defines from but they aren't in alignment with what openimageio has.
Cheers
Samuel.
Looking into it further as i attempted to build 1.8 with python3 and it wont detect it, so there is a problem with the cmake find scripts its using.
cmake .. \
-DUSE_PYTHON=ON \
-DPYTHON_VERSION:STRING=2.7 \
-DUSE_OPENSSL=ON \
-DCMAKE_INSTALL_PREFIX=/usr \
-DCMAKE_INSTALL_LIBDIR=lib \
-DOIIO_BUILD_TESTS=OFF \
-DOIIO_BUILD_TOOLS=ON
make
cp src/python/OpenImageIO.so src/python/OpenImageIO-2.7.so
if [ -f CMakeCache.txt ]; then rm CMakeCache.txt; fi
cmake .. \
-DUSE_PYTHON=ON \
-DPYTHON_VERSION:STRING=3.7 \
-DUSE_OPENSSL=ON \
-DCMAKE_INSTALL_PREFIX=/usr \
-DCMAKE_INSTALL_LIBDIR=lib \
-DOIIO_BUILD_TESTS=OFF \
-DOIIO_BUILD_TOOLS=ON
make
and something equivalent for the installation portion which manually copies the OpenImageIO-2.7.so into the python 2.7 site packages.
tar tf openimageio-1.8.17-3-x86_64.pkg.tar.xz | grep python
usr/lib/python3.7/
usr/lib/python3.7/site-packages/
usr/lib/python3.7/site-packages/OpenImageIO.so
So I'm pushing a new rel of the package with fixed CMake flags but identical binary content.