Dear Manish,
It looks like this is caused by a bug which is already fixed in our master branch, but unfortunately the fix is not in the latest release.
One solution is to get the master branch from the repository. Alternatively, I think this is only a problem when compiling with the NEKTAR_USE_MESHGEN option. If you don't need this functionality, switching it off in cmake should help.
Cheers,
Douglas
Dear All,
I am trying to compile the latest version of the code, nektar++-4.3.3, and I am getting the following error:
In file included from /home/manish/nektar++-4.3.3/library/NekMeshUtils/SurfaceMeshing/CurveMesh.h:44:0,
from /home/manish/nektar++-4.3.3/library/NekMeshUtils/SurfaceMeshing/CurveMesh.cpp:36:
/home/manish/nektar++-4.3.3/library/NekMeshUtils/Octree/Octree.h:76:18: error: ‘string’ does not name a type
const string uds)
^
/home/manish/nektar++-4.3.3/library/NekMeshUtils/Octree/Octree.h:183:5: error: ‘string’ does not name a type
string m_udsfile;
^
/home/manish/nektar++-4.3.3/library/NekMeshUtils/Octree/Octree.h: In constructor ‘Nektar::NekMeshUtils::Octree::Octree(Nektar::NekMeshUtils::CADSystemSharedPtr, bool, Nektar::NekDouble, Nektar::NekDouble, Nektar::NekDouble,
int)’:
/home/manish/nektar++-4.3.3/library/NekMeshUtils/Octree/Octree.h:78:27: error: class ‘Nektar::NekMeshUtils::Octree’ does not have any field named ‘m_udsfile’
m_verbose(ver), m_udsfile(uds)
^
library/NekMeshUtils/CMakeFiles/NekMeshUtils.dir/build.make:307: recipe for target 'library/NekMeshUtils/CMakeFiles/NekMeshUtils.dir/SurfaceMeshing/CurveMesh.cpp.o' failed
make[2]: *** [library/NekMeshUtils/CMakeFiles/NekMeshUtils.dir/SurfaceMeshing/CurveMesh.cpp.o] Error 1
CMakeFiles/Makefile2:904: recipe for target 'library/NekMeshUtils/CMakeFiles/NekMeshUtils.dir/all' failed
make[1]: *** [library/NekMeshUtils/CMakeFiles/NekMeshUtils.dir/all] Error 2
Makefile:146: recipe for target 'all' failed
make: *** [all] Error 2
This error showed up when compiling the 4.3.2 version of the code too.
What could I be doing wrong, and how can I resolve it?
Looking forward to hearing from you soon.
Thank you,
Manish Sharma