Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR.
Chuck, thank you very much for the info. This is most useful. Frank. From: Chuck Atkins [mailto:chuck.atk...@kitware.com] Sent: Dienstag, 11. Oktober 2016 21:28 To: Albina, Frank Subject: Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR. b)Use the configuration option paraview_FROM_GIT:BOOL=ON to check out the latest paraview sources (which will be 5.2.0 RC1) Almost. Setting paraview_FROM_GIT=ON will use the latest paraview sources which is the git master branch and a few commits ahead of RC1. The sb has been updated to use the RC1 source tarball so if you set paraview_FROM_GIT=OFF then you'll get the source for 5.2.0-RC1. So FROM_GIT=OFF gives you 5.2.0-RC1 and FROM_GIT=On gives you whatever is in master, which right now is "v5.2.0-RC1-7-g52f2ad6" which means 7 commits past RC1. ___ 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
Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR.
Hi Frank, I tracked down the problem. The way the superbuild was calling ./configure for mesa was causing the default -O2 flags set by mesa's ./configure to get dropped, thus resulting in an unoptimized mesa build. I just merged a fix for both issues into the superbuild. -- Chuck Atkins Staff R&D Engineer, Scientific Computing Kitware, Inc. On Fri, Oct 7, 2016 at 4:39 PM, Chuck Atkins wrote: > 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. >> > > I see the same problem. I have a fix for the packaging and will get it up > shortly. It probably won't make it for the RC tonight but it will be fixed > before the release. > > > 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. >> > > The good news is that I was just able to reproduce the problem. Even > better I could isolate it to the mesa build from the superbuild. Swapping > out the mesa libs in the release binary on the web site, on a single > 14-Core Haswell CPU I see a difference of 25MiPolys / sec with the > superbuild libraries vs 118MiPolys / sec with the website binaries. > That's roughly a 4.5x performance difference, i.e. not good. I don't know > yet if it's a mesa problem or how we build it. I'll dig deeper and let you > know. > > Thanks for the bug! > > - Chuck > ___ 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
Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR.
> > 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. > I see the same problem. I have a fix for the packaging and will get it up shortly. It probably won't make it for the RC tonight but it will be fixed before the release. 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. > The good news is that I was just able to reproduce the problem. Even better I could isolate it to the mesa build from the superbuild. Swapping out the mesa libs in the release binary on the web site, on a single 14-Core Haswell CPU I see a difference of 25MiPolys / sec with the superbuild libraries vs 118MiPolys / sec with the website binaries. That's roughly a 4.5x performance difference, i.e. not good. I don't know yet if it's a mesa problem or how we build it. I'll dig deeper and let you know. Thanks for the bug! - Chuck ___ 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
Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR.
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
Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR.
Chuck, thanks to your help, I could compile ParaView v5.1.2 with Mesa v12.0.3 (release version, not from GIT repository) using the master git checkout (hash 26eb1fa8f5364242d9f9c03b598f0ee735cf88e4) from last week. It was not easy but probably due my lack of experience using the superbuild system and not knowing which external projects I had to enable/disable. A few comments regarding the build on my system (OpenSuSE 12.3): 1. Cmake v3.6.x is required for building. Not a big deal but this is new wrt. the release checkout. 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 For these libraries, I had to specify in the cmake file the additional option –libdir=/lib 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” 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. I have let my standard benchmark running to give you some numbers. The benchmark consists in rendering pressure-contours on a generic F1 & sports car as shown hereafter. The surface mesh of the sports car is roughly twice as fine as on the F1 car. [cid:image001.jpg@01D2208D.A36EF080] Rendering time Generic F1 car Generic sports car PV 5.1.2 binary 27.06s 77.95s PV 5.1.2 MESA3D v12.0.3 81.10s 272.05s From the comparison, the version compiled with MESA 3D v12.0.3 is slower by a factor of 3 to 3.5. The compiler used is gcc v4.8.5 and in all cases the same server has been used. The SWR AVX2 rendering was set by giving –mesa-swr-avx2 from the command line for the downloaded binary, by setting the environment variable GALLIUM_DRIVER=swr for the compiled version. Is this something which was expected? Or did I miss something when compiling the source code? Thank you very much in advance for any feedback. Cheers, Frank. From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Albina, Frank Sent: Donnerstag, 29. September 2016 13:55 To: Chuck Atkins; Ben Boeckel Cc: Del Citto, Francesco; paraview@paraview.org Subject: Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR. Hi Chuck, Thank you very much for your reply. It is very interesting and I will try my best to get ParaView compiled following your recommendations. Unfortunately, others duties are holding me off this week from concentrating on this but I will share my test results comparing ParaView on GPU, with mesa-llvm and mesa-swr-avx2. Talk to you soon. Best regards, Frank. From: Chuck Atkins [mailto:chuck.atk...@kitware.com] Sent: Mittwoch, 28. September 2016 21:18 To: Ben Boeckel Cc: Albina, Frank; David E DeMarle; Del Citto, Francesco; paraview@paraview.org<mailto:paraview@paraview.org> Subject: Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR. > My intention is to compile paraview without GUI to run it in batch on > our cluster. This is the main reason why I am using a specific test > suite to check the performance of mesa-llvm vs. mesa-swr vs. GPU. At > the moment, on CPUs supporting AVX2 instruction set, mesa-swr shows a > very decent performance. Hence, my interest also to try out the latest > mesa 12.0.3 version, which I have downloaded today and started > compiling. In this regard, do you have any configuration options you > can share for use in offscreen mode? If this is handled already by the > latest superbuild version, then please disregard the questions above. Chuck (Cc'd) does this quite a bit. There are scripts he has committed which are used to build for specific platforms which you may be able to start using, but he's the best source of instructions for those. Hi Frank, The updated superbuild uses a common shared set of packages that we use for several different projects and then the top level project which is ParaView specific. To use this, you'll want to check out the current master branch in the paraview-superbuild, run "git submodule init", and then "git submodule update". This will put you at the current state of things. You can browse the build script I have committed in Scripts/sites for linux clusters and Cray systems at Los Alamos National Labs and the DoD HPC network. They but they're a bit complicated though as I use them in a very generic fashion with lots of options for a lot of different build configurations. The gist of it though is to encode all of the options you would need to turn on in a pre-configured CMake cache script.
Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR.
Hi Chuck, Thank you very much for your reply. It is very interesting and I will try my best to get ParaView compiled following your recommendations. Unfortunately, others duties are holding me off this week from concentrating on this but I will share my test results comparing ParaView on GPU, with mesa-llvm and mesa-swr-avx2. Talk to you soon. Best regards, Frank. From: Chuck Atkins [mailto:chuck.atk...@kitware.com] Sent: Mittwoch, 28. September 2016 21:18 To: Ben Boeckel Cc: Albina, Frank; David E DeMarle; Del Citto, Francesco; paraview@paraview.org Subject: Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR. > My intention is to compile paraview without GUI to run it in batch on > our cluster. This is the main reason why I am using a specific test > suite to check the performance of mesa-llvm vs. mesa-swr vs. GPU. At > the moment, on CPUs supporting AVX2 instruction set, mesa-swr shows a > very decent performance. Hence, my interest also to try out the latest > mesa 12.0.3 version, which I have downloaded today and started > compiling. In this regard, do you have any configuration options you > can share for use in offscreen mode? If this is handled already by the > latest superbuild version, then please disregard the questions above. Chuck (Cc'd) does this quite a bit. There are scripts he has committed which are used to build for specific platforms which you may be able to start using, but he's the best source of instructions for those. Hi Frank, The updated superbuild uses a common shared set of packages that we use for several different projects and then the top level project which is ParaView specific. To use this, you'll want to check out the current master branch in the paraview-superbuild, run "git submodule init", and then "git submodule update". This will put you at the current state of things. You can browse the build script I have committed in Scripts/sites for linux clusters and Cray systems at Los Alamos National Labs and the DoD HPC network. They but they're a bit complicated though as I use them in a very generic fashion with lots of options for a lot of different build configurations. The gist of it though is to encode all of the options you would need to turn on in a pre-configured CMake cache script. Note that this is actually a CMake script that sets the initial cache values and not and not just a list of variables like in CMakeCache.txt . See cmake/sites for a few examples. Doing this simplifies your build to just: cd /path/to/build/location cmake -C /path/to/MySystem-Cache.cmake /path/to/superbuild/source # no -j here but don't worry, the subprojects will build in parallel make # Make the resulting ParaView package ctest -R cpack-paraview-TGZ The end result is ParaView-5.1.2-OpenGL2-MPI-Linux-64bit.tar.gz that you can extract anywhere to install. Using ctest to drive the packaging is a bit weird, I know, but trust me that there were various reasons for that which could warrant it's own separate thread. This allows you to keep MySystem-Cache.cmake under source control to maintain a consistent build. For your configuration, the specific options of interest to run on are ENABLE_osmesa and ENABLE_ospray. Our default configuration of osmesa will enable SWR. What you'll end up with is a pvserver / pvbatch that uses OSMesa for off-screen CPU based rendering without X but with both llvmpipe and swr drivers built. You can switch between the by setting the GALLIUM_DRIVER env var to either llvmpipe or swr. Hope that gives you a good place to get started. ___ 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
Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR.
> > > My intention is to compile paraview without GUI to run it in batch on > > our cluster. This is the main reason why I am using a specific test > > suite to check the performance of mesa-llvm vs. mesa-swr vs. GPU. At > > the moment, on CPUs supporting AVX2 instruction set, mesa-swr shows a > > very decent performance. Hence, my interest also to try out the latest > > mesa 12.0.3 version, which I have downloaded today and started > > compiling. In this regard, do you have any configuration options you > > can share for use in offscreen mode? If this is handled already by the > > latest superbuild version, then please disregard the questions above. > > Chuck (Cc'd) does this quite a bit. There are scripts he has committed > which are used to build for specific platforms which you may be able to > start using, but he's the best source of instructions for those. > Hi Frank, The updated superbuild uses a common shared set of packages that we use for several different projects and then the top level project which is ParaView specific. To use this, you'll want to check out the current master branch in the paraview-superbuild, run "git submodule init", and then "git submodule update". This will put you at the current state of things. You can browse the build script I have committed in Scripts/sites for linux clusters and Cray systems at Los Alamos National Labs and the DoD HPC network. They but they're a bit complicated though as I use them in a very generic fashion with lots of options for a lot of different build configurations. The gist of it though is to encode all of the options you would need to turn on in a pre-configured CMake cache script. Note that this is actually a CMake script that sets the initial cache values and not and not just a list of variables like in CMakeCache.txt . See cmake/sites for a few examples. Doing this simplifies your build to just: cd /path/to/build/location cmake -C /path/to/MySystem-Cache.cmake /path/to/superbuild/source # no -j here but don't worry, the subprojects will build in parallel make # Make the resulting ParaView package ctest -R cpack-paraview-TGZ The end result is ParaView-5.1.2-OpenGL2-MPI-Linux-64bit.tar.gz that you can extract anywhere to install. Using ctest to drive the packaging is a bit weird, I know, but trust me that there were various reasons for that which could warrant it's own separate thread. This allows you to keep MySystem-Cache.cmake under source control to maintain a consistent build. For your configuration, the specific options of interest to run on are ENABLE_osmesa and ENABLE_ospray. Our default configuration of osmesa will enable SWR. What you'll end up with is a pvserver / pvbatch that uses OSMesa for off-screen CPU based rendering without X but with both llvmpipe and swr drivers built. You can switch between the by setting the GALLIUM_DRIVER env var to either llvmpipe or swr. Hope that gives you a good place to get started. ___ 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
Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR.
On Wed, Sep 28, 2016 at 17:54:53 +0200, Albina, Frank wrote: > I had to recompile from scractch, which took a bit of time. Actually, > the GNU compiler requirement is coming from building the OSPRAY > project, as shown hereafter: > > [...] > CMake Error at cmake/gcc.cmake:48 (MESSAGE): > GCC version 4.8.0 or greater is required to build OSPRay. > Call Stack (most recent call first): > cmake/ospray.cmake:97 (INCLUDE) > common/CMakeLists.txt:17 (CONFIGURE_OSPRAY) This makes sense; ospray requires C++11 support for which GCC 4.8 was the first release with viable support (4.7.x had some, but not enough). > If the new superbuild has support for building mesa 12.0.3, I would be > interested in trying this out. Are there any instructions I can follow > to do that? It's on my list to improve docs here. I'd welcome feedback where the existing docs are deficient (they're in README.md on the master branch) so I can improve those parts. > My intention is to compile paraview without GUI to run it in batch on > our cluster. This is the main reason why I am using a specific test > suite to check the performance of mesa-llvm vs. mesa-swr vs. GPU. At > the moment, on CPUs supporting AVX2 instruction set, mesa-swr shows a > very decent performance. Hence, my interest also to try out the latest > mesa 12.0.3 version, which I have downloaded today and started > compiling. In this regard, do you have any configuration options you > can share for use in offscreen mode? If this is handled already by the > latest superbuild version, then please disregard the questions above. Chuck (Cc'd) does this quite a bit. There are scripts he has committed which are used to build for specific platforms which you may be able to start using, but he's the best source of instructions for those. --Ben ___ 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
Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR.
Ben, Thank you very much for the information in your email. >> 3. You need a GNU compiler v4.8.0 or above to build. My Linux >> distribution comes with gcc v4.7.2. Fortunately, I had gcc v4.9.2 >> installed with which I could perform a successful build. > What subproject required this? I had to recompile from scractch, which took a bit of time. Actually, the GNU compiler requirement is coming from building the OSPRAY project, as shown hereafter: [...] CMake Error at cmake/gcc.cmake:48 (MESSAGE): GCC version 4.8.0 or greater is required to build OSPRay. Call Stack (most recent call first): cmake/ospray.cmake:97 (INCLUDE) common/CMakeLists.txt:17 (CONFIGURE_OSPRAY) -- Configuring incomplete, errors occurred! [...] > The new superbuild has support for building mesa 12.0.3 as part of the build. > We used prebuilt binaries before because our build machine was Debian 6 which > was not easily capable of compiling the LLVM -> Mesa chain > without a > self-compiled compiler and such, so it was built once and that was it. I > think it did contain SWR since it was a git snapshot. > Utkarsh? As additional information, I have cloned the git repository and did: git checkout origin/release which I then used to build Paraview V5.1.2 along with all dependencies. If the new superbuild has support for building mesa 12.0.3, I would be interested in trying this out. Are there any instructions I can follow to do that? My intention is to compile paraview without GUI to run it in batch on our cluster. This is the main reason why I am using a specific test suite to check the performance of mesa-llvm vs. mesa-swr vs. GPU. At the moment, on CPUs supporting AVX2 instruction set, mesa-swr shows a very decent performance. Hence, my interest also to try out the latest mesa 12.0.3 version, which I have downloaded today and started compiling. In this regard, do you have any configuration options you can share for use in offscreen mode? If this is handled already by the latest superbuild version, then please disregard the questions above. Thanks a lot in advance. Regards, Frank. -Original Message- From: Ben Boeckel [mailto:ben.boec...@kitware.com] Sent: Mittwoch, 28. September 2016 14:45 To: Albina, Frank Cc: David E DeMarle; Del Citto, Francesco; paraview@paraview.org Subject: Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR. On Wed, Sep 28, 2016 at 10:06:15 +0200, Albina, Frank wrote: > In this regard, I would like to point out a few things I have found > while performing the build process on the aforementioned Linux > distribution. Note that my incentive is to help improve the ParaView > software suite as well as helping others to be able to build and use > the software. Thanks for the feedback. Responses inline. > 2. You definitely need cmake at least cmake v3.5 (and not v3.3) to > compile ParaView from SuperBuild. Ah, ParaView is 3.3, but the superbuild is 3.5. As a heads up, the new superbuild which will be used for ParaView 5.2 will require at least 3.6.1. > 3. You need a GNU compiler v4.8.0 or above to build. My Linux > distribution comes with gcc v4.7.2. Fortunately, I had gcc v4.9.2 > installed with which I could perform a successful build. What subproject required this? > 4. Dependencies such libsz, libxml, libbzip2 are built and stored > in the /install/lib64 directory on my platform. This creates > linking issues which I could partly resolve by pushing the missing > libraries into the /install/lib directory. This is not ideal > but could be solved by forcing the lib directory to > /install/lib using the --libdir option. Hrm. I'm on Fedora (which also uses lib64) and though I had gotten all the lib64-isms out of the superbuild. Maybe I had missed some before 5.1.2 (the superbuild now uses common infrastructure shared between other similar superbuilds). > 5. The vistrails plugin cannot be built. After 3 attempts, the git > clone from https://kwgitlab.kitware.com/paraview/vistrails.git fails. > Either the link is wrong or the server is unreachable. vistrails should be hidden behind a "USE_NONFREE_COMPONENTS" flag. vistrails (and acusolve) are not FOSS, so their git repos are on our internal server. > 6. The mesa libraries are pre-compiled and downloaded to > /mesa-downloads. They are unpacked and moved into the ParaView > installation directory when performing “make install”. These libraries > are dating from May 3rd, hence prior to the release of Mesa 12.0 which > embeds OpenSWR as a build option. Is there a way to build new libGL.so > and libOSMesa.so libraries based on Mesa3D v12.0 and replace the > currently pre-compiled binaries? If so,what are the typical > configuration options used in this case? The new superbuild has support for buildin
Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR.
On Wed, Sep 28, 2016 at 10:06:15 +0200, Albina, Frank wrote: > In this regard, I would like to point out a few things I have found > while performing the build process on the aforementioned Linux > distribution. Note that my incentive is to help improve the ParaView > software suite as well as helping others to be able to build and use > the software. Thanks for the feedback. Responses inline. > 2. You definitely need cmake at least cmake v3.5 (and not v3.3) to > compile ParaView from SuperBuild. Ah, ParaView is 3.3, but the superbuild is 3.5. As a heads up, the new superbuild which will be used for ParaView 5.2 will require at least 3.6.1. > 3. You need a GNU compiler v4.8.0 or above to build. My Linux > distribution comes with gcc v4.7.2. Fortunately, I had gcc v4.9.2 > installed with which I could perform a successful build. What subproject required this? > 4. Dependencies such libsz, libxml, libbzip2 are built and stored > in the /install/lib64 directory on my platform. This creates > linking issues which I could partly resolve by pushing the missing > libraries into the /install/lib directory. This is not ideal > but could be solved by forcing the lib directory to > /install/lib using the --libdir option. Hrm. I'm on Fedora (which also uses lib64) and though I had gotten all the lib64-isms out of the superbuild. Maybe I had missed some before 5.1.2 (the superbuild now uses common infrastructure shared between other similar superbuilds). > 5. The vistrails plugin cannot be built. After 3 attempts, the git > clone from https://kwgitlab.kitware.com/paraview/vistrails.git fails. > Either the link is wrong or the server is unreachable. vistrails should be hidden behind a "USE_NONFREE_COMPONENTS" flag. vistrails (and acusolve) are not FOSS, so their git repos are on our internal server. > 6. The mesa libraries are pre-compiled and downloaded to > /mesa-downloads. They are unpacked and moved into the ParaView > installation directory when performing “make install”. These libraries > are dating from May 3rd, hence prior to the release of Mesa 12.0 which > embeds OpenSWR as a build option. Is there a way to build new libGL.so > and libOSMesa.so libraries based on Mesa3D v12.0 and replace the > currently pre-compiled binaries? If so,what are the typical > configuration options used in this case? The new superbuild has support for building mesa 12.0.3 as part of the build. We used prebuilt binaries before because our build machine was Debian 6 which was not easily capable of compiling the LLVM -> Mesa chain without a self-compiled compiler and such, so it was built once and that was it. I think it did contain SWR since it was a git snapshot. Utkarsh? --Ben ___ 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
Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR.
On Wed, Sep 28, 2016 at 4:06 AM, Albina, Frank < frank.alb...@sauber-motorsport.com> wrote: > David, > > > > I could manage to get Paraview 5.1.2 compiled using the ParaView > superbuild on my Linux desktop running OpenSuSE 12.3. > > > > In this regard, I would like to point out a few things I have found while > performing the build process on the aforementioned Linux distribution. Note > that my incentive is to help improve the ParaView software suite as well as > helping others to be able to build and use the software. > > Thanks, we appreciate it! > > 1. I found it this page quite useful for having at least a starting > point for building ParaView v5.1.2 on Linux: https://cmake.org/Wiki/ > ParaView/Binaries > > 2. You definitely need cmake at least *cmake v3.5* (and not v3.3) to > compile ParaView from SuperBuild. > Ah yes, sorry for the misinformation on my part. > 3. You need a *GNU compiler v4.8.0 or above* to build. My Linux > distribution comes with gcc v4.7.2. Fortunately, I had gcc v4.9.2 installed > with which I could perform a successful build. > > 4. Dependencies such libsz, libxml, libbzip2 are built and stored in > the /install/lib64 directory on my platform. This creates linking > issues which I could partly resolve by pushing the missing libraries into > the /install/lib directory. This is not ideal but could be solved by > forcing the lib directory to /install/lib using the --libdir option. > > 5. The vistrails plugin cannot be built. After 3 attempts, the git > clone from https://kwgitlab.kitware.com/paraview/vistrails.git fails. > Either the link is wrong or the server is unreachable. > > 6. The mesa libraries are pre-compiled and downloaded to > /mesa-downloads. They are unpacked and moved into the ParaView > installation directory when performing “make install”. These libraries are > dating from May 3rd, hence prior to the release of Mesa 12.0 which embeds > OpenSWR as a build option. Is there a way to build new libGL.so and > libOSMesa.so libraries based on Mesa3D v12.0 and replace the currently > pre-compiled binaries? If so,what are the typical configuration options > used in this case? > > I believe the plan is to update to 12 before 5.2. Is that right @chuck and @ben? > Any feedback/comments are most welcome. > > > > Regards, > > > Frank. > > > > *From:* Albina, Frank > *Sent:* Montag, 26. September 2016 15:51 > *To:* 'David E DeMarle' > *Cc:* paraview@paraview.org; Del Citto, Francesco > *Subject:* RE: [Paraview] Building ParaView v5.1.2 on Linux from source > with support for GPU and SWR. > > > > Perfect! > > > > Thanks. > > > > Frank. > > > > *From:* David E DeMarle [mailto:dave.dema...@kitware.com > ] > *Sent:* Montag, 26. September 2016 15:49 > > *To:* Albina, Frank > *Cc:* paraview@paraview.org; Del Citto, Francesco > *Subject:* Re: [Paraview] Building ParaView v5.1.2 on Linux from source > with support for GPU and SWR. > > > > 3.3 > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > > > On Mon, Sep 26, 2016 at 9:42 AM, Albina, Frank motorsport.com> wrote: > > Hi David! > > > > Thanks for the swift feedback. As I have been compiling ParaView from > source for at least the last 6 years, it never came to my mind trying out > the super-build. £ > > > > I’ll try it out and report if I find myself stuck. > > > > By the way, which CMake version do you recommend for building ParaView > v5.1.2 from the git repository? > > > > Best regards, > > > Frank. > > > > *From:* David E DeMarle [mailto:dave.dema...@kitware.com] > *Sent:* Montag, 26. September 2016 15:37 > *To:* Albina, Frank > *Cc:* paraview@paraview.org; Del Citto, Francesco > *Subject:* Re: [Paraview] Building ParaView v5.1.2 on Linux from source > with support for GPU and SWR. > > > > I recommend the ParaView superbuild. All of the incantations that we use > to setup and build paraview, mesa and the rest of our dependencies are > written down and maintained there. > > https://gitlab.kitware.com/paraview/paraview-superbuild > > We've used it for our Desktop binaries for years, and more and more often > we use it for our HPC installs as well. > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > > > On Mon, Sep 26, 2016 at 5:17 AM, Albina, Frank motorsport.com> wrote: > > Dear all, > > after having downloaded last we
Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR.
David, I could manage to get Paraview 5.1.2 compiled using the ParaView superbuild on my Linux desktop running OpenSuSE 12.3. In this regard, I would like to point out a few things I have found while performing the build process on the aforementioned Linux distribution. Note that my incentive is to help improve the ParaView software suite as well as helping others to be able to build and use the software. 1. I found it this page quite useful for having at least a starting point for building ParaView v5.1.2 on Linux: https://cmake.org/Wiki/ParaView/Binaries 2. You definitely need cmake at least cmake v3.5 (and not v3.3) to compile ParaView from SuperBuild. 3. You need a GNU compiler v4.8.0 or above to build. My Linux distribution comes with gcc v4.7.2. Fortunately, I had gcc v4.9.2 installed with which I could perform a successful build. 4. Dependencies such libsz, libxml, libbzip2 are built and stored in the /install/lib64 directory on my platform. This creates linking issues which I could partly resolve by pushing the missing libraries into the /install/lib directory. This is not ideal but could be solved by forcing the lib directory to /install/lib using the --libdir option. 5. The vistrails plugin cannot be built. After 3 attempts, the git clone from https://kwgitlab.kitware.com/paraview/vistrails.git fails. Either the link is wrong or the server is unreachable. 6. The mesa libraries are pre-compiled and downloaded to /mesa-downloads. They are unpacked and moved into the ParaView installation directory when performing “make install”. These libraries are dating from May 3rd, hence prior to the release of Mesa 12.0 which embeds OpenSWR as a build option. Is there a way to build new libGL.so and libOSMesa.so libraries based on Mesa3D v12.0 and replace the currently pre-compiled binaries? If so,what are the typical configuration options used in this case? Any feedback/comments are most welcome. Regards, Frank. From: Albina, Frank Sent: Montag, 26. September 2016 15:51 To: 'David E DeMarle' Cc: paraview@paraview.org; Del Citto, Francesco Subject: RE: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR. Perfect! Thanks. Frank. From: David E DeMarle [mailto:dave.dema...@kitware.com] Sent: Montag, 26. September 2016 15:49 To: Albina, Frank Cc: paraview@paraview.org<mailto:paraview@paraview.org>; Del Citto, Francesco Subject: Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR. 3.3 David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Sep 26, 2016 at 9:42 AM, Albina, Frank mailto:frank.alb...@sauber-motorsport.com>> wrote: Hi David! Thanks for the swift feedback. As I have been compiling ParaView from source for at least the last 6 years, it never came to my mind trying out the super-build. £ I’ll try it out and report if I find myself stuck. By the way, which CMake version do you recommend for building ParaView v5.1.2 from the git repository? Best regards, Frank. From: David E DeMarle [mailto:dave.dema...@kitware.com<mailto:dave.dema...@kitware.com>] Sent: Montag, 26. September 2016 15:37 To: Albina, Frank Cc: paraview@paraview.org<mailto:paraview@paraview.org>; Del Citto, Francesco Subject: Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR. I recommend the ParaView superbuild. All of the incantations that we use to setup and build paraview, mesa and the rest of our dependencies are written down and maintained there. https://gitlab.kitware.com/paraview/paraview-superbuild We've used it for our Desktop binaries for years, and more and more often we use it for our HPC installs as well. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Sep 26, 2016 at 5:17 AM, Albina, Frank mailto:frank.alb...@sauber-motorsport.com>> wrote: 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
Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR.
Perfect! Thanks. Frank. From: David E DeMarle [mailto:dave.dema...@kitware.com] Sent: Montag, 26. September 2016 15:49 To: Albina, Frank Cc: paraview@paraview.org; Del Citto, Francesco Subject: Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR. 3.3 David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Sep 26, 2016 at 9:42 AM, Albina, Frank mailto:frank.alb...@sauber-motorsport.com>> wrote: Hi David! Thanks for the swift feedback. As I have been compiling ParaView from source for at least the last 6 years, it never came to my mind trying out the super-build. £ I’ll try it out and report if I find myself stuck. By the way, which CMake version do you recommend for building ParaView v5.1.2 from the git repository? Best regards, Frank. From: David E DeMarle [mailto:dave.dema...@kitware.com<mailto:dave.dema...@kitware.com>] Sent: Montag, 26. September 2016 15:37 To: Albina, Frank Cc: paraview@paraview.org<mailto:paraview@paraview.org>; Del Citto, Francesco Subject: Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR. I recommend the ParaView superbuild. All of the incantations that we use to setup and build paraview, mesa and the rest of our dependencies are written down and maintained there. https://gitlab.kitware.com/paraview/paraview-superbuild We've used it for our Desktop binaries for years, and more and more often we use it for our HPC installs as well. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Sep 26, 2016 at 5:17 AM, Albina, Frank mailto:frank.alb...@sauber-motorsport.com>> wrote: 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<http://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 ___ 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
Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR.
3.3 David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Sep 26, 2016 at 9:42 AM, Albina, Frank < frank.alb...@sauber-motorsport.com> wrote: > Hi David! > > > > Thanks for the swift feedback. As I have been compiling ParaView from > source for at least the last 6 years, it never came to my mind trying out > the super-build. £ > > > > I’ll try it out and report if I find myself stuck. > > > > By the way, which CMake version do you recommend for building ParaView > v5.1.2 from the git repository? > > > > Best regards, > > > Frank. > > > > *From:* David E DeMarle [mailto:dave.dema...@kitware.com] > *Sent:* Montag, 26. September 2016 15:37 > *To:* Albina, Frank > *Cc:* paraview@paraview.org; Del Citto, Francesco > *Subject:* Re: [Paraview] Building ParaView v5.1.2 on Linux from source > with support for GPU and SWR. > > > > I recommend the ParaView superbuild. All of the incantations that we use > to setup and build paraview, mesa and the rest of our dependencies are > written down and maintained there. > > https://gitlab.kitware.com/paraview/paraview-superbuild > > We've used it for our Desktop binaries for years, and more and more often > we use it for our HPC installs as well. > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > > > On Mon, Sep 26, 2016 at 5:17 AM, Albina, Frank motorsport.com> wrote: > > 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 > > > ___ 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
Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR.
Hi David! Thanks for the swift feedback. As I have been compiling ParaView from source for at least the last 6 years, it never came to my mind trying out the super-build. £ I’ll try it out and report if I find myself stuck. By the way, which CMake version do you recommend for building ParaView v5.1.2 from the git repository? Best regards, Frank. From: David E DeMarle [mailto:dave.dema...@kitware.com] Sent: Montag, 26. September 2016 15:37 To: Albina, Frank Cc: paraview@paraview.org; Del Citto, Francesco Subject: Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR. I recommend the ParaView superbuild. All of the incantations that we use to setup and build paraview, mesa and the rest of our dependencies are written down and maintained there. https://gitlab.kitware.com/paraview/paraview-superbuild We've used it for our Desktop binaries for years, and more and more often we use it for our HPC installs as well. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Sep 26, 2016 at 5:17 AM, Albina, Frank mailto:frank.alb...@sauber-motorsport.com>> wrote: 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<http://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 ___ 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
Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR.
I recommend the ParaView superbuild. All of the incantations that we use to setup and build paraview, mesa and the rest of our dependencies are written down and maintained there. https://gitlab.kitware.com/paraview/paraview-superbuild We've used it for our Desktop binaries for years, and more and more often we use it for our HPC installs as well. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Sep 26, 2016 at 5:17 AM, Albina, Frank < frank.alb...@sauber-motorsport.com> wrote: > 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/opensou > rce/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 > > ___ 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
[Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR.
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
