You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 9, 2022. It is now read-only.
I've managed to compile thirdParty libs, however compilation of FOAM-FSI itself also have some problems. Compilation produces a lot of "cannot open file" for headers of foam-extend. If checked the WM_PROJECT_DIR variable, it is OK. Maybe you know what can be the reason of such messages ? Or is it a normal situation ??
sergey@sergey-Notebook-PC:~/foam/foam-extend-3.2/FOAM-FSI$ ./Allwmake
+++ dirname ./Allwmake
++ cd .
++ pwd
+ DIR=/home/sergey/foam/foam-extend-3.2/FOAM-FSI
+ cd /home/sergey/foam/foam-extend-3.2/FOAM-FSI
+ wmakeLnInclude src/boundaryConditions
+ wmakeLnInclude src/fvSchemes
+ wmakeLnInclude src/fsi
+ wmakeLnInclude src/RBFMeshMotionSolver
+ wmakeLnInclude src/SRFModelAbs
+ wmake libso src/boundaryConditions
SOURCE=SDCMovingWallVelocity/SDCMovingWallVelocityFvPatchVectorField.C ; mpicxx -m64 -Dlinux64 -DWM_DP -Wall -Wextra -Werror -O3 -DNDEBUG -DNDEBUG -DNDEBUG -DNDEBUG -DNDEBUG -DNDEBUG -DNoRepository -ftemplate-depth-200 -std=c++11 -isystem /home/sergey/foam/foam-extend-3.2/src/finiteVolume/lnInclude -isystem ../fsi/lnInclude -isystem ../fsi -isystem ../thirdParty/eigen -isystem ../thirdParty/yaml-cpp/install/include -isystem ../thirdParty/boost -IlnInclude -I. -I/home/sergey/foam/foam-extend-3.2/src/foam/lnInclude -I/home/sergey/foam/foam-extend-3.2/src/OSspecific/POSIX/lnInclude -fPIC -c $SOURCE -o Make/linux64GccDPOpt/SDCMovingWallVelocityFvPatchVectorField.o
'/home/sergey/foam/foam-extend-3.2/lib/linux64GccDPOpt/libboundaryConditions.so' is up to date.
+ wmake libso src/fvSchemes
wmakeLnInclude: linking include files to ./lnInclude
Making dependency list for source file ddtSchemes/bdf2/bdf2DdtSchemes.C
Making dependency list for source file ddtSchemes/bdf1/bdf1DdtSchemes.C
could not open file ddtScheme.H for source file ddtSchemes/bdf1/bdf1DdtSchemes.C
could not open file volFields.H for source file ddtSchemes/bdf1/bdf1DdtSchemes.C
could not open file ddtScheme.H for source file ddtSchemes/bdf2/bdf2DdtSchemes.C
could not open file surfaceInterpolate.H for source file ddtSchemes/bdf2/bdf2DdtSchemes.C
could not open file fvcDiv.H for source file ddtSchemes/bdf2/bdf2DdtSchemes.C
could not open file fvMatrices.H for source file ddtSchemes/bdf2/bdf2DdtSchemes.C
could not open file slipFvPatchFields.H for source file ddtSchemes/bdf2/bdf2DdtSchemes.C
could not open file symmetryFvPatchFields.H for source file ddtSchemes/bdf2/bdf2DdtSchemes.C
could not open file basicSymmetryFvPatchFields.H for source file ddtSchemes/bdf2/bdf2DdtSchemes.C
could not open file fvMesh.H for source file ddtSchemes/bdf2/bdf2DdtSchemes.C
could not open file surfaceInterpolate.H for source file ddtSchemes/bdf1/bdf1DdtSchemes.C
could not open file fvcDiv.H for source file ddtSchemes/bdf1/bdf1DdtSchemes.C
could not open file fvMatrices.H for source file ddtSchemes/bdf1/bdf1DdtSchemes.C
could not open file slipFvPatchFields.H for source file ddtSchemes/bdf1/bdf1DdtSchemes.C
could not open file symmetryFvPatchFields.H for source file ddtSchemes/bdf1/bdf1DdtSchemes.C
could not open file basicSymmetryFvPatchFields.H for source file ddtSchemes/bdf1/bdf1DdtSchemes.C
could not open file fvMesh.H for source file ddtSchemes/bdf1/bdf1DdtSchemes.C
Making dependency list for source file d2dt2Schemes/backward2D2dt2/backward2D2dt2Schemes.C
could not open file d2dt2Scheme.H for source file d2dt2Schemes/backward2D2dt2/backward2D2dt2Schemes.C
could not open file fvcDiv.H for source file d2dt2Schemes/backward2D2dt2/backward2D2dt2Schemes.C
could not open file fvMatrices.H for source file d2dt2Schemes/backward2D2dt2/backward2D2dt2Schemes.C
could not open file backwardDdtScheme.H for source file d2dt2Schemes/backward2D2dt2/backward2D2dt2Schemes.C
could not open file fvMesh.H for source file d2dt2Schemes/backward2D2dt2/backward2D2dt2Schemes.C
Making dependency list for source file d2dt2Schemes/Euler1D2dt2/Euler1D2dt2Schemes.C
could not open file d2dt2Scheme.H for source file d2dt2Schemes/Euler1D2dt2/Euler1D2dt2Schemes.C
could not open file fvcDiv.H for source file d2dt2Schemes/Euler1D2dt2/Euler1D2dt2Schemes.C
could not open file fvMatrices.H for source file d2dt2Schemes/Euler1D2dt2/Euler1D2dt2Schemes.C
could not open file fvMesh.H for source file d2dt2Schemes/Euler1D2dt2/Euler1D2dt2Schemes.C
SOURCE=ddtSchemes/bdf1/bdf1DdtSchemes.C ; mpicxx -m64 -Dlinux64 -DWM_DP -Wall -Wextra -Werror -O3 -DNDEBUG -DNDEBUG -DNDEBUG -DNDEBUG -DNDEBUG -DNDEBUG -DNoRepository -ftemplate-depth-200 -isystem /home/sergey/foam/foam-extend-3.2/src/finiteVolume/lnInclude -IlnInclude -I. -I/home/sergey/foam/foam-extend-3.2/src/foam/lnInclude -I/home/sergey/foam/foam-extend-3.2/src/OSspecific/POSIX/lnInclude -fPIC -c $SOURCE -o Make/linux64GccDPOpt/bdf1DdtSchemes.o
SOURCE=ddtSchemes/bdf2/bdf2DdtSchemes.C ; mpicxx -m64 -Dlinux64 -DWM_DP -Wall -Wextra -Werror -O3 -DNDEBUG -DNDEBUG -DNDEBUG -DNDEBUG -DNDEBUG -DNDEBUG -DNoRepository -ftemplate-depth-200 -isystem /home/sergey/foam/foam-extend-3.2/src/finiteVolume/lnInclude -IlnInclude -I. -I/home/sergey/foam/foam-extend-3.2/src/foam/lnInclude -I/home/sergey/foam/foam-extend-3.2/src/OSspecific/POSIX/lnInclude -fPIC -c $SOURCE -o Make/linux64GccDPOpt/bdf2DdtSchemes.o
^Cmake: *** [Make/linux64GccDPOpt/bdf1DdtSchemes.o] Interrupt
make: *** [Make/linux64GccDPOpt/bdf2DdtSchemes.o] Interrupt
The text was updated successfully, but these errors were encountered:
yeah, that is a bit confusing. foam-extend uses a bit dated build system. the "could not open" messages are because I use "-isystem" flags during the compilation of the sources. Apparently wmake doesn't understand that flag, but it should compile just fine.
I've managed to compile thirdParty libs, however compilation of FOAM-FSI itself also have some problems. Compilation produces a lot of "cannot open file" for headers of foam-extend. If checked the WM_PROJECT_DIR variable, it is OK. Maybe you know what can be the reason of such messages ? Or is it a normal situation ??
The text was updated successfully, but these errors were encountered: