Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compile own LibRaw for OIIO? #121

Open
jfpanisset opened this issue Jun 29, 2021 · 0 comments
Open

Compile own LibRaw for OIIO? #121

jfpanisset opened this issue Jun 29, 2021 · 0 comments

Comments

@jfpanisset
Copy link
Contributor

jfpanisset commented Jun 29, 2021

OpenImageIO's oiiotool builds and links against LibRaw: since the base image for the ASWF containers is nvidia/cudalgl:${ASWF_CUDA_VERSION}-devel-centos7 that brings a recent version of CentOS 7, in the build I'm looking at CentOS 7.8 which installs LibRaw-0.19.4-1.el7.x86_64.rpm

Thus /usr/local/bin/oiiotool has an explicit dependency on a system installed libraw 0.19 DSO:

# ldd oiiotool | grep libraw
	libraw_r.so.19 => /lib64/libraw_r.so.19 (0x00007f97b33bf000)

Unfortunately earlier, still fairly widely used versions of CentOS (for instance CentOS 7.6) has an earlier libraw version, LibRaw-0.14.8-5.el7.20120830git98d925.x86_64.rpm which installs an earlier versioned libraw_r.so.5:

/lib64/libraw_r.so.5 -> libraw_r.so.5.0.0
/lib64/libraw_r.so.5.0.0

In the spirit of having ASWF container builds depend as little as possible on "system installed" components (especially for libraries which are particularly relevant to ASWF projects such as libraw), would it make sense to add libraw as an explicit build instead of depending on the system installed version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant