Re: OpenVDB Jenkins builds broken due to Boost Python not found


Larry Gritz
 

As an aside, VFX Platform is, as they have repeated many times, not a list of endorsed or fundamental packages, but rather an agreement of versions for particular packages that have been historically problematic and plagued by "versionitis" (particularly in how they were used by Foundry, Autodesk, and Side Effects).

VFX Platform is great at that mission, I'm not knocking what they're doing.

But there is a separate, currently nonexistent, but badly needed list of core packages and versions that more accurately forms the basis of a modern VFX software stack, and that is the list that our CI is going to need to cater to. It overlaps VFX Platform somewhat, but is mostly a super-set. 

Whoever is scoping the work for these things must remember that VFX Platform not the complete list of the packages that need to be available as core dependencies and that need to be included in the matrix of interoperability that we are trying to test with CI. And also that we will need a "version next" entry in the test matrix that intentionally defies both lists by building all the TOT checkouts against each other, so that we can catch upcoming incompatibilities early as part of the review/CI process for PRs.




On Wed, Oct 31, 2018 at 5:38 AM Aloys Baillet <aloys.baillet@...> wrote:
Hi Thanh,

I've been reading a bit more about Packer and indeed it should be a fairly easy thing to setup a docker image that matches the VFX platform.
One reason I've been angling towards Docker is that NVidia (which most VFX studio have lots of hardware from) provides a very rich set of base images that allow us to build against GL and CUDA libraries, which some VFX packages have optional dependencies to (especially OpenSubdiv).
Having pre-built GL-enabled variants of these packages might be desirable, especially Qt which is quite tricky to build properly and all the vendors provide in slightly different variations...

That said, to get started on the official VFX platform 2018 you would just need a vanilla CentOS-7 VM/docker image and run this:

yum install -y centos-release-scl-rh
yum install -y devtoolset-7-toolchain make
source /opt/rh/devtoolset-7/enable

Then install cmake using this:
cmake-3.12.3-Linux-x86_64.sh --skip-license 
(the cmake in centos7 is way too old...)

Cheers,

Aloys



--
Larry Gritz
lg@...

Join main@lists.aswf.io to automatically receive all group messages.