Hi Frank, > 2. There are still libraries built into /path/to/build/install/lib64. > > · projects/apple-unix/szip.cmake > > · projects/unix/mesa.common.cmake > > · projects/apple-unix/freetye.cmake >
These should not need to be part of the resulting install and can be left out of the final packaging. The build/install tree is a staging area that only gets selectively pruned from for the final packaging. 3. Building Mesa v12.0.3 works like a charm. However, the libOSMesa > relies on additional libraries such as: > > · libglapi.so > > · libswrAVX.so > > · libswrAVX2.so > > which are not copied into the archive when packing the binaries using: > “ctest -V -R cpack-paraviewsdk-TGZ” > This should have been fixed a while ago. I'll try to reproduce it and make sure the packaging is correct. > 4. Compared to the ParaView v5.1.2 binary for Linux, the compiled > version with mesa v12.0.3 is substantially slower than with the OpenSWR > version shipped with the binary. > That certainly should not be the case. Do you get the same SWR debugging messages on both showing: SWR create screen! This processor supports AVX2. If those messages are missing then you're not rendering with OpenSWR (cernotly not the desired result). Are youy running pverver as an MPI job? If so, how many processes per node vs CPU cores per node?
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
