ThirdParty-common issueshttps://develop.openfoam.com/Development/ThirdParty-common/-/issues2024-03-27T16:38:12Zhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/67Introducing MUI code coupling library into OpenFOAM2024-03-27T16:38:12ZWendi LiuIntroducing MUI code coupling library into OpenFOAM## Functionality to add/problem to solve
Integrate the code coupling library [Multiscale Universal Interface](https://mxui.github.io/) in OpenFOAM as a third-party library to couple OpenFOAM with other solvers or OpenFOAM with itself.
...## Functionality to add/problem to solve
Integrate the code coupling library [Multiscale Universal Interface](https://mxui.github.io/) in OpenFOAM as a third-party library to couple OpenFOAM with other solvers or OpenFOAM with itself.
## Target audience
Users who want to couple OpenFOAM with other solvers or OpenFOAM with itself.
## Proposal
A working general integration of MUI is proposed by applying the following patch to the ThirdParty repository.
[muiIntegrationTP.patch](/uploads/9b0637fcc8137a818b65f31875d6e40f/muiIntegrationTP.patch)
Below is a summarise of what have been added and modified.
- Modified `Allwmake` to include script to build MUI.
- Added build script `makeMUI.`
- Added MUI related patch file `etc/patches/MUI-2.0` to resolve ambiguity issue between MUI-v2.0 and OpenFOAM. We have merged the changes into the MUI repository, so that no patch files will be needed in future MUI releases.
- Updated `BUILD.md` and `SOURCES.md` to include MUI related documentations.
## Related issue
[openfoam issue #3127](https://develop.openfoam.com/Development/openfoam/-/issues/3127)
## What does success look like, and how can we measure that?
The Patch has been tested with the ThirdParty development repository (commit 7ff69fa1a733b45b069a387fd0c275b15b7f2150).
The proposed changes can be patched and tested as follows
- Clone Development Repositories
```
git clone https://develop.openfoam.com/Development/ThirdParty-common.git
git clone https://develop.openfoam.com/Development/openfoam.git
```
- Obtain the MUI source file in the ThirdParty Repository
```
cd ThirdParty-common/sources
mkdir mui && cd mui
wget https://github.com/MxUI/MUI/archive/refs/tags/2.0.tar.gz
tar -xf 2.0.tar.gz && rm 2.0.tar.gz
```
- Obtain and place patches in Repositories
- Patch
```
cd openfoam/
patch -p2 < muiIntegrationOF.patch
rm muiIntegrationOF.patch
cd ../ThirdParty-common/
patch -p2 < muiIntegrationTP.patch
rm muiIntegrationTP.patch
```
- Change permission of newly added files if needed
- Enable MUI support (MUI is disabled by default)
- Modify L37 of `openfoam/etc/config.sh` to change `mui_version=MUI-none` into `mui_version=MUI-2.0`
- Source and Allwmake
```
cd openfoam/
source etc/bashrc
./Allwmake -j 4
```
- Test MUI enabled OpenFOAM
```
cd openfoam/applications/test/coupling-MUI
./testCase/Allrun
cd openfoam/tutorials/basic/laplacianFoamMUI
./AllrunCoupled
```
If MUI library successfully integrated, the following log messages can be found for the `coupling-MUI` unit test.
```
...
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time
Create mesh for time = 0
```
If MUI library successfully integrated, the following log messages can be found for the `laplacianFoamMUI` tutorial.
```
....
MUI [lib_mpi_multidomain]: Rank: 2, "domain2" registered interface "interface_twoD_1" as 59a4e385
MUI [lib_mpi_multidomain]: Rank: 3, "domain2" registered interface "interface_twoD_1" as 59a4e385
MUI Info [lib_mpi_multidomain]: 1 distinct interface(s) found
MUI [lib_mpi_multidomain]: Setting up interface interface_twoD_1 [59a4e385] (rank ids are local to each interface)
MUI [comm_mpi.h]: Rank: 3, Identifier: mpi://domain2/interface_twoD_1, Domain size: 2, Peers: 2
MUI [comm_mpi.h]: Rank: 2, Identifier: mpi://domain2/interface_twoD_1, Domain size: 2, Peers: 2
MUI [comm_mpi.h]: Rank: 1, Identifier: mpi://domain1/interface_twoD_1, Domain size: 2, Peers: 2
MUI [comm_mpi.h]: Rank: 0, Identifier: mpi://domain1/interface_twoD_1, Domain size: 2, Peers: 2
MUI [lib_mpi_multidomain]: Rank: 2, "domain2" registered interface "interface_threeD_1" as 31f80b7e
MUI [lib_mpi_multidomain]: Rank: 1, "domain1" registered interface "interface_threeD_1" as 31f80b7e
MUI [lib_mpi_multidomain]: Rank: 3, "domain2" registered interface "interface_threeD_1" as 31f80b7e
MUI [lib_mpi_multidomain]: Rank: 0, "domain1" registered interface "interface_threeD_1" as 31f80b7e
MUI Info [lib_mpi_multidomain]: 1 distinct interface(s) found
MUI [lib_mpi_multidomain]: Setting up interface interface_threeD_1 [31f80b7e] (rank ids are local to each interface)
MUI [comm_mpi.h]: Rank: 0, Identifier: mpi://domain1/interface_threeD_1, Domain size: 2, Peers: 2
MUI [comm_mpi.h]: Rank: 3, Identifier: mpi://domain2/interface_threeD_1, Domain size: 2, Peers: 2
MUI [comm_mpi.h]: Rank: 2, Identifier: mpi://domain2/interface_threeD_1, Domain size: 2, Peers: 2
MUI [comm_mpi.h]: Rank: 1, Identifier: mpi://domain1/interface_threeD_1, Domain size: 2, Peers: 2
MUI [lib_mpi_multidomain]: Rank: 2, "domain2" registered interface "interface_T_1" as 4a5523ab
MUI [lib_mpi_multidomain]: Rank: 1, "domain1" registered interface "interface_T_1" as 4a5523ab
MUI [lib_mpi_multidomain]: Rank: 0, "domain1" registered interface "interface_T_1" as 4a5523ab
MUI [lib_mpi_multidomain]: Rank: 3, "domain2" registered interface "interface_T_1" as 4a5523ab
MUI Info [lib_mpi_multidomain]: 1 distinct interface(s) found
MUI [lib_mpi_multidomain]: Setting up interface interface_T_1 [4a5523ab] (rank ids are local to each interface)
MUI [comm_mpi.h]: Rank: 0, Identifier: mpi://domain1/interface_T_1, Domain size: 2, Peers: 2
MUI [comm_mpi.h]: Rank: 1, Identifier: mpi://domain1/interface_T_1, Domain size: 2, Peers: 2
MUI [comm_mpi.h]: Rank: 3, Identifier: mpi://domain2/interface_T_1, Domain size: 2, Peers: 2
MUI [comm_mpi.h]: Rank: 2, Identifier: mpi://domain2/interface_T_1, Domain size: 2, Peers: 2
Calculating temperature distribution
Calculating temperature distribution
Time = 0.005
Time = 0.005
MUI interface "domain1"/"interface_twoD_1" value committed: 1 at Iteration = 0
MUI interface "domain2"/"interface_twoD_1" value committed: 1 at Iteration = 0
MUI interface "domain1"/"interface_threeD_1" value committed: 2 at Iteration = 0
MUI interface "domain1"/"interface_T_1" value committed: 3 at Iteration = 0
MUI interface "domain2"/"interface_threeD_1" value committed: 2 at Iteration = 0
MUI interface "domain2"/"interface_T_1" value committed: 3 at Iteration = 0
DICPCG: Solving for T, Initial residual = 1, Final residual = 8.33243e-07, No Iterations 7
DICPCG: Solving for T, Initial residual = 0.00446911, Final residual = 7.14892e-07, No Iterations 4
DICPCG: Solving for T, Initial residual = 0.000148123, Final residual = 6.63323e-07, No Iterations 2
MUI interface "domain1"/"interface_twoD_1" value fetched: 1 at Iteration = 0
MUI interface "domain1"/"interface_threeD_1" value fetched: 2 at Iteration = 0
MUI interface "domain1"/"interface_T_1" value fetched: 3 at Iteration = 0
ExecutionTime = 0.07 s ClockTime = 0 s
Time = 0.01
MUI interface "domain1"/"interface_twoD_1" value committed: 1 at Iteration = 1
MUI interface "domain1"/"interface_threeD_1" value committed: 2 at Iteration = 1
MUI interface "domain1"/"interface_T_1" value committed: 3 at Iteration = 1
DICPCG: Solving for T, Initial residual = 0.203755, Final residual = 1.57027e-07, No Iterations 7
DICPCG: Solving for T, Initial residual = 0.00184337, Final residual = 2.32416e-07, No Iterations 4
DICPCG: Solving for T, Initial residual = 1, Final residual = 8.33243e-07, No Iterations 7
DICPCG: Solving for T, Initial residual = 5.70921e-05, Final residual = 2.8776e-07, No Iterations 2
DICPCG: Solving for T, Initial residual = 0.00446911, Final residual = 7.14892e-07, No Iterations 4
DICPCG: Solving for T, Initial residual = 0.000148123, Final residual = 6.63323e-07, No Iterations 2
MUI interface "domain2"/"interface_twoD_1" value fetched: 1 at Iteration = 0
MUI interface "domain2"/"interface_threeD_1" value fetched: 2 at Iteration = 0
MUI interface "domain2"/"interface_T_1" value fetched: 3 at Iteration = 0
ExecutionTime = 0.1 s ClockTime = 0 s
Time = 0.01
MUI interface "domain2"/"interface_twoD_1" value committed: 1 at Iteration = 1
MUI interface "domain2"/"interface_threeD_1" value committed: 2 at Iteration = 1
MUI interface "domain2"/"interface_T_1" value committed: 3 at Iteration = 1
MUI interface "domain1"/"interface_twoD_1" value fetched: 1 at Iteration = 1
MUI interface "domain1"/"interface_threeD_1" value fetched: 2 at Iteration = 1
MUI interface "domain1"/"interface_T_1" value fetched: 3 at Iteration = 1
ExecutionTime = 0.08 s ClockTime = 0 s
Time = 0.015
MUI interface "domain1"/"interface_twoD_1" value committed: 1 at Iteration = 2
MUI interface "domain1"/"interface_threeD_1" value committed: 2 at Iteration = 2
MUI interface "domain1"/"interface_T_1" value committed: 3 at Iteration = 2
DICPCG: Solving for T, Initial residual = 0.109922, Final residual = 4.92455e-07, No Iterations 6
DICPCG: Solving for T, Initial residual = 0.00104616, Final residual = 7.0666e-07, No Iterations 3
DICPCG: Solving for T, Initial residual = 3.13839e-05, Final residual = 1.66653e-07, No Iterations 2
DICPCG: Solving for T, Initial residual = 0.203755, Final residual = 1.57027e-07, No Iterations 7
DICPCG: Solving for T, Initial residual = 0.00184337, Final residual = 2.32416e-07, No Iterations 4
DICPCG: Solving for T, Initial residual = 5.70921e-05, Final residual = 2.8776e-07, No Iterations 2
MUI interface "domain2"/"interface_twoD_1" value fetched: 1 at Iteration = 1
MUI interface "domain2"/"interface_threeD_1" value fetched: 2 at Iteration = 1
MUI interface "domain2"/"interface_T_1" value fetched: 3 at Iteration = 1
ExecutionTime = 0.11 s ClockTime = 1 s
Time = 0.015
MUI interface "domain2"/"interface_twoD_1" value committed: 1 at Iteration = 2
MUI interface "domain2"/"interface_threeD_1" value committed: 2 at Iteration = 2
MUI interface "domain2"/"interface_T_1" value committed: 3 at Iteration = 2
DICPCG: Solving for T, Initial residual = 0.109922, Final residual = 4.92455e-07, No Iterations 6
MUI interface "domain1"/"interface_twoD_1" value fetched: 1 at Iteration = 2
MUI interface "domain1"/"interface_threeD_1" value fetched: 2 at Iteration = 2
MUI interface "domain1"/"interface_T_1" value fetched: 3 at Iteration = 2
ExecutionTime = 0.1 s ClockTime = 1 s
...
```https://develop.openfoam.com/Development/ThirdParty-common/-/issues/66When I compile ADIOS2 using makeAdios script and the dev tool set from CENTOS...2023-01-27T11:19:57ZJuan Díaz GonzálezWhen I compile ADIOS2 using makeAdios script and the dev tool set from CENTOS in CENTOS I am get in an errorWhen I compile ADIOS2 using makeAdios script and the dev tool set from CENTOS in CENTOS I am get in an error.
The error that I have is this:
`[ 46%] Building C object testing/utils/cwriter/CMakeFiles/Test.Utils.CWriter.dir/TestUtilsCWri...When I compile ADIOS2 using makeAdios script and the dev tool set from CENTOS in CENTOS I am get in an error.
The error that I have is this:
`[ 46%] Building C object testing/utils/cwriter/CMakeFiles/Test.Utils.CWriter.dir/TestUtilsCWriter.c.o`
[ 46%] Building C object testing/adios2/performance/manyvars/CMakeFiles/PerfManyVars.dir/PerfManyVars.c.o`
[ 46%] Linking C executable ../../../bin/Test.Utils.CWriter`
[ 46%] Linking C executable ../../../../bin/PerfManyVars`
`/opt/rh/devtoolset-8/root/usr/libexec/gcc/x86_64-redhat-linux/8/ld: /opt/rh/devtoolset-8/root/usr/lib/gcc/x86_64-redhat-linux/8//libstdc++_nonshared.a(functexcept48.o): undefined reference to symbol '__cxa_free_exception@@CXXABI_1.3'`
`/usr/lib64/libstdc++.so.6: error adding symbols: DSO missing from command line`
`make[2]: *** [testing/utils/cwriter/CMakeFiles/Test.Utils.CWriter.dir/build.make:99: bin/Test.Utils.CWriter] Error 1`
`make[1]: *** [CMakeFiles/Makefile2:8571: testing/utils/cwriter/CMakeFiles/Test.Utils.CWriter.dir/all] Error 2`
`make[1]: *** Waiting for unfinished jobs....`
`/opt/rh/devtoolset-8/root/usr/libexec/gcc/x86_64-redhat-linux/8/ld: /opt/rh/devtoolset-8/root/usr/lib/gcc/x86_64-`redhat-linux/8//libstdc++_nonshared.a(functexcept48.o): undefined reference to symbol '__cxa_free_exception@@CXXABI_1.3'`
`/usr/lib64/libstdc++.so.6: error adding symbols: DSO missing from command line`
make[2]: *** [testing/adios2/performance/manyvars/CMakeFiles/PerfManyVars.dir/build.make:99: bin/PerfManyVars] `Error 1`
`make[1]: *** [CMakeFiles/Makefile2:8253: testing/adios2/performance/manyvars/CMakeFiles/PerfManyVars.dir/all] Error 2`
`[ 46%] Linking CXX executable ../../bin/adios2_reorganize_mpi`
`[ 46%] Built target adios_reorganize_mpi`
`[ 46%] Linking CXX executable ../../bin/bpls`
`[ 46%] Built target bpls`
`[ 46%] Linking CXX shared library ../../lib64/libadios2_cxx11.so`
`[ 46%] Built target adios2_cxx11`
`make: *** [Makefile:146: all] Error 2`
`Error building: ADIOS2-2.8.3`https://develop.openfoam.com/Development/ThirdParty-common/-/issues/65Incorrect download links for METIS during compilation2022-08-04T14:44:02ZDanyal MohaddesIncorrect download links for METIS during compilation# Summary
The download links for METIS provided during ThirdParty compilation are out of date.
# Steps to Reproduce
1. Download the latest version of ThirdParty (v2206)
2. `./Allwmake`
# Current Behavior
When METIS compilation is reach...# Summary
The download links for METIS provided during ThirdParty compilation are out of date.
# Steps to Reproduce
1. Download the latest version of ThirdParty (v2206)
2. `./Allwmake`
# Current Behavior
When METIS compilation is reached (and skipped), the links provided to download METIS are to [this link](http://glaros.dtc.umn.edu/gkhome/metis/metis/overview) and [this link](http://glaros.dtc.umn.edu/gkhome/fetch/sw/metis/metis-5.1.0.tar.gz). These links are out of date; the package has since moved.
# Correct Behavior
The link provided to download METIS should be [this one](https://github.com/KarypisLab/METIS).
# Possible fix
Update the links in `BUILD.md`https://develop.openfoam.com/Development/ThirdParty-common/-/issues/64Paraview:5.10.0: catalyst building issue2022-08-04T11:32:33ZPawan GhildiyalParaview:5.10.0: catalyst building issueHi ,
I am using latest release paraview as updated in sourceforge 5.10.0 release.
Build paraview successfully using mesa-llvm and it compiled well.
runTimepostprocessing : compiles well and work well. However catalyst
fail t...Hi ,
I am using latest release paraview as updated in sourceforge 5.10.0 release.
Build paraview successfully using mesa-llvm and it compiled well.
runTimepostprocessing : compiles well and work well. However catalyst
fail to compile with following error. (Note this issue is not there with Paraview-5.10.RC2)
![image](/uploads/b377779ef8b2fda54268a1761d94008a/image.png)Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/63build problems with Paraview-5.10 and gcc482021-12-31T13:28:05ZPrashant Sonakarbuild problems with Paraview-5.10 and gcc48Various problems noted (probably not to be fixed) and workarounds to get it compilingVarious problems noted (probably not to be fixed) and workarounds to get it compilinghttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/62Cgal/boost does not properly set -toolset parameter when using non gcc compiler.2021-12-15T18:39:06ZFelix LeClairCgal/boost does not properly set -toolset parameter when using non gcc compiler.When etc/bashrc has wm_compiler set to use the intel compiler suite (Icc), and wmake all | ./Allmake is called, cgal and boost do no have the -toolset variable set to pass -toolset=intel-linux to makeCGAL.
related to bootsrap.sh is tha...When etc/bashrc has wm_compiler set to use the intel compiler suite (Icc), and wmake all | ./Allmake is called, cgal and boost do no have the -toolset variable set to pass -toolset=intel-linux to makeCGAL.
related to bootsrap.sh is that it does not seem to pass 'openmpi yes ;' causing performance degradationshttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/61paraview openfoam reader does not like symbolic dimensions2023-06-26T13:36:53ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comparaview openfoam reader does not like symbolic dimensionsWith symbolic dimensions (`writeUnits` in `etc/controlDict`) it will write the dimensions for a dimless field as:
```
dimensions [];
```
This crashes the built-in openfoam reader:
```
[paraview ] vtkOpenFOAMReader.cxx:7184 ...With symbolic dimensions (`writeUnits` in `etc/controlDict`) it will write the dimensions for a dimless field as:
```
dimensions [];
```
This crashes the built-in openfoam reader:
```
[paraview ] vtkOpenFOAMReader.cxx:7184 ERR| vtkOpenFOAMReaderPrivate (0x55cbc0ba2f70): Error reading line 18 of CAEME_AutoGapClosure/15/cellToZone: Expected a number, found a non-digit character ]
```Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/60script updates2021-03-29T10:24:25ZMark OLESENscript updates- scripts need updates for newer mesa, paraview etc.
@Prashant- scripts need updates for newer mesa, paraview etc.
@PrashantMark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/59Change default WM_NCOMPPROCS2021-03-23T16:55:17ZGuanyang XueChange default WM_NCOMPPROCSI was warned by the HPC manager that the third party make script uses all CPU cores in the head node.
Could you please consider adding a script to change the default behavior if it detects HPC environment?
For example, run `lscpu | gre...I was warned by the HPC manager that the third party make script uses all CPU cores in the head node.
Could you please consider adding a script to change the default behavior if it detects HPC environment?
For example, run `lscpu | grep Socket`. If the result is 2, ask the user if it's in HPC environment, then type in no. of cores (most HPC managers are OK with `-j 4`).https://develop.openfoam.com/Development/ThirdParty-common/-/issues/58build optimized version of PETSc by default?2020-12-23T09:30:56Zstefano zampinibuild optimized version of PETSc by default?Currently, https://develop.openfoam.com/Development/ThirdParty-common/-/blob/master/makePETSC configures PETSc in debug mode.
We should add `--with-debugging=0` unless some openFOAM debug build variable is on. PETSc will be up to 10x fas...Currently, https://develop.openfoam.com/Development/ThirdParty-common/-/blob/master/makePETSC configures PETSc in debug mode.
We should add `--with-debugging=0` unless some openFOAM debug build variable is on. PETSc will be up to 10x faster in non-debug mode. @mark ?Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/57better support for cross-compiling2020-08-14T04:42:48ZMark OLESENbetter support for cross-compilingMark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/56ADIOS recompiles although already compiled2020-08-18T15:51:01ZHåkanADIOS recompiles although already compiled### Summary
ADIOS recompiles although already compiled
### Steps to reproduce
Follow the installation procedure of v2006. The problem is in the file https://sourceforge.net/projects/openfoam/files/v2006/ThirdParty-v2006.tgz. Running ....### Summary
ADIOS recompiles although already compiled
### Steps to reproduce
Follow the installation procedure of v2006. The problem is in the file https://sourceforge.net/projects/openfoam/files/v2006/ThirdParty-v2006.tgz. Running ./Allwmake several times, it is not noted that ADIOS is already compiled, so it compiles again. The problem is that the check if it is installed looks for a lib64 directory, while the compilation of ADIOS creates a lib directory. It can be fixed by:
pushd $ADIOS2_ARCH_PATH; ln -s lib lib64; popd
However, it would be better if the test is modified to do it correctly, or if the ADIOS compilation produces a lib64 directory directly.
### Example case
See above
### What is the current *bug* behaviour?
ADIOS recompiles although already compiled
### What is the expected *correct* behavior?
ADIOS should not be compiled if it is already compiled.
### Relevant logs and/or images
The Allwmake command gives output that ADIOS is recompiled.
### Environment information
- OpenFOAM version : v2006
- Operating system : Ubuntu 20.04
- Hardware info : N/A
- Compiler : N/A
### Possible fixes
makeAdios2, line 30:
if [ -d "$dir/include" -a -r "$dir/lib$WM_COMPILER_LIB_ARCH/libadios2$EXT_SO" ]
The $WM_COMPILER_LIB_ARCH needs to be removed, or the problem needs to be fixed some other way.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/55remove libz dependency for scotch2020-08-07T12:18:46ZMark OLESENremove libz dependency for scotch- compression handling is only useful for reading in graph files, which we don't use. Removing it reduces the number of ThirdParty interdependencies.
@Prashant- compression handling is only useful for reading in graph files, which we don't use. Removing it reduces the number of ThirdParty interdependencies.
@PrashantMark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/54handle Fujitsu version of mpicc2021-03-22T14:12:57ZMark OLESENhandle Fujitsu version of mpiccas noted in https://develop.openfoam.com/Development/openfoam/-/issues/1671
- mpifcc vs mpicc
- mpiFCC vs mpicxx
@t-karatsuas noted in https://develop.openfoam.com/Development/openfoam/-/issues/1671
- mpifcc vs mpicc
- mpiFCC vs mpicxx
@t-karatsuMark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/53Paraview- with python and openmpi>42020-07-09T15:11:49ZPrashant SonakarParaview- with python and openmpi>4Placeholder to resolve issues when building
- Paraview-5.6.3
- Python-2.7
- Openmpi-4.0.3
This fails with mp4py issue as reported in https://gitlab.kitware.com/vtk/vtk/-/issues/17544
We might need a patch for 5.6.3 version or upgrade t...Placeholder to resolve issues when building
- Paraview-5.6.3
- Python-2.7
- Openmpi-4.0.3
This fails with mp4py issue as reported in https://gitlab.kitware.com/vtk/vtk/-/issues/17544
We might need a patch for 5.6.3 version or upgrade to new Paraview ??
@mark @andyv2012https://develop.openfoam.com/Development/ThirdParty-common/-/issues/52paraview building2021-04-17T08:04:39ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comparaview building@mark to pull in the requirements can we rephrase as something:
openSUSE
The easiest way of obtaining Paraview is to install the binary version:
```
sudo zypper install paraview-devel
```
Unfortunately this does not install enough to...@mark to pull in the requirements can we rephrase as something:
openSUSE
The easiest way of obtaining Paraview is to install the binary version:
```
sudo zypper install paraview-devel
```
Unfortunately this does not install enough to build our paraFoam reader. However installing above should pull in all the dependencies to build Paraview with our scripts.
If this does not work one can install the dependencies oneselves. The following subset may be enough:
sudo zypper install Mesa-libEGL-devel
sudo zypper install libqt5-qtbase-devel libqt5-qtsvg-devel libqt5-qttools-devel libqt5-qtx11extras
sudo zypper install libXt-devel
```https://develop.openfoam.com/Development/ThirdParty-common/-/issues/50error to compile ./makeParaView2020-06-10T15:52:37ZJoaquin Osseserror to compile ./makeParaViewI'm following all the instruction in the OpenFOAM webpage to install it on Ubuntu 20.04 version
First I did this as the instructions says;
cd $WM_THIRD_PARTY_DIR
./makeParaView
And I received this message;
./makeParaView: 64: local:...I'm following all the instruction in the OpenFOAM webpage to install it on Ubuntu 20.04 version
First I did this as the instructions says;
cd $WM_THIRD_PARTY_DIR
./makeParaView
And I received this message;
./makeParaView: 64: local: -DWM_DP: bad variable name
./makeParaView: 64: -DOPENFOAM: bad variable name
Thankshttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/49issues with ptscotch and mingw2020-06-26T08:12:25ZMark OLESENissues with ptscotch and mingwAppears that we might need the following in the Makefile:
```
CCD = gcc -I$(MPI_ARCH_PATH)/include
```
@PawanAppears that we might need the following in the Makefile:
```
CCD = gcc -I$(MPI_ARCH_PATH)/include
```
@PawanMark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/48Compilation of paraview5.6.3 does not start.2020-07-22T11:05:07Zsariew8Compilation of paraview5.6.3 does not start.$ ~/OpenFOAM/ThirdParty-common$ ./makeParaView \
./makeParaView: 64: local: -DWM_DP: bad variable name \
./makeParaView: 64: ./makeParaView: -DOPENFOAM: bad variable name
did i make another mistakes?$ ~/OpenFOAM/ThirdParty-common$ ./makeParaView \
./makeParaView: 64: local: -DWM_DP: bad variable name \
./makeParaView: 64: ./makeParaView: -DOPENFOAM: bad variable name
did i make another mistakes?Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/46add pkgconfig management/handling to makePETSC2020-06-26T08:05:52ZMark OLESENadd pkgconfig management/handling to makePETSCRelated to suggestion by @szampini - we should address pkgconfig contents when using makePETSC (as per the makeQT handling) to ensure things are movableRelated to suggestion by @szampini - we should address pkgconfig contents when using makePETSC (as per the makeQT handling) to ensure things are movableMark OLESENMark OLESEN