Dear all, after having downloaded last week the latest ParaView release (v5.1.2) for Linux, I have found out that the binary version has the following folder structure in lib/paraview-5.1: mesa-llvm |-- libGL.so -> libGL.so.1 |-- libGL.so.1 -> libGL.so.1.5 |-- libGL.so.1.5 |-- libOSMesa.so -> libOSMesa.so.8 |-- libOSMesa.so.8 -> libOSMesa.so.8.0.0 `-- libOSMesa.so.8.0.0 mesa-swr-avx |-- libGL.so -> libGL.so.1 |-- libGL.so.1 -> libGL.so.1.5 |-- libGL.so.1.5 |-- libOSMesa.so -> libOSMesa.so.8 |-- libOSMesa.so.8 -> libOSMesa.so.8.0.0 `-- libOSMesa.so.8.0.0 mesa-swr-avx2 |-- libGL.so -> libGL.so.1 |-- libGL.so.1 -> libGL.so.1.5 |-- libGL.so.1.5 |-- libOSMesa.so -> libOSMesa.so.8 |-- libOSMesa.so.8 -> libOSMesa.so.8.0.0 `-- libOSMesa.so.8.0.0 Which is an elegant way of providing a binary package for GPU and non-GPU architectures at the same time. Hence my question: How do I build ParaView v5.1.2 from source to have the same folder structure so that I have one version for GPU and software rendering? I understand that swr-avx(2) should be also available from Mesa v12.x. Is there anything I'd need to consider / take care of before building the different OSMesa libraries with LLVM / OpenSWR? Frank Albina
_______________________________________________ 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
