ThirdParty-common issueshttps://develop.openfoam.com/Development/ThirdParty-common/-/issues2018-06-11T09:48:04Zhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/37makeParaview - BUILD_SUFFIX2018-06-11T09:48:04ZPrashant SonakarmakeParaview - BUILD_SUFFIX- using makeParaview with mesa leads to installation in e.g. ParaView-5.5.0`-mesa`
- whereas the etc/config.*sh/paraview search for existence of ParaView-5.5.0 to set up ParaView_INCLUDE_DIR etc.
- another issue is search for \*-qt\* ins...- using makeParaview with mesa leads to installation in e.g. ParaView-5.5.0`-mesa`
- whereas the etc/config.*sh/paraview search for existence of ParaView-5.5.0 to set up ParaView_INCLUDE_DIR etc.
- another issue is search for \*-qt\* instead of \*qt\*, which leads to failure in setting up Qt5_DIR, needed for building PVReaders.
using qt-5.6.3 and ParaView-5.5.0v1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/30Check for wmake toolchain in some third-party components2018-06-28T08:31:14ZMark OLESENCheck for wmake toolchain in some third-party componentsIf ThirdParty Allwmake is executed prior to the OpenFOAM Allwmake, the wmkdep and dirToString will not yet exist. Emit a warning about this and/or take some corrective action.
Mentioned in exchange#583
If ThirdParty Allwmake is executed prior to the OpenFOAM Allwmake, the wmkdep and dirToString will not yet exist. Emit a warning about this and/or take some corrective action.
Mentioned in exchange#583
v1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/29more stringency when exporting WM_ compiler settings2018-05-29T10:42:24ZMark OLESENmore stringency when exporting WM_ compiler settings- for building 3rd-party components, we export `WM_CC` and `WM_CXX` compiler settings as `CC` and `CXX` so the configure/CMake know about them. However, when trying to build something like Clang we can experience issues. The OpenFOAM env...- for building 3rd-party components, we export `WM_CC` and `WM_CXX` compiler settings as `CC` and `CXX` so the configure/CMake know about them. However, when trying to build something like Clang we can experience issues. The OpenFOAM env sets ThirdParty Clang (setting WM_CC in the process), but this is the component we are trying to build, so `makeLLVM` will have problems configuring for this non-existent compiler.
1. can avoid this by using `makeLLVM -gcc` to force use of gcc for making Clang. This seems to be an ok alternative, since this isn't part of the normal OpenFOAM process (we are building the toolchain for building OpenFOAM).
2. check within the ThirdParty scripts that the exported `CC` variable corresponds to a command. Eg,
if test -n "$WM_CC" && command -v "$WM_CC" >/dev/null
then
export CC="$WM_CC"
[ -n "$WM_CFLAGS" ] && export CFLAGS="$WM_CFLAGS"
fi
Probably the second one is OK to include too, but targeted for the next release.v1806Mark OLESENMark OLESEN