Ask about using Cross-patch meshing with compounds to generate surface meshes in the gmsh compiled version
Hi,I am a beginner in gmsh software, I have successfully compiled the source code of gmsh under windows environment with VS2022 and cmake, but using the set compound function under the compiled version of gmsh causes problems in some models, but these problems don't occur under the exe version from the gmsh website. The error reporting model is in appendix 1, (the file EADS Mako_HEAT.geo records the set compound operation of EADS Mako_HEAT.stp), and these two files have to be placed in a folder to ensure that .geofile.The direct error is shown in Figure 1. I looked at the source code to see exactly where the error is reported, it is in the parameterised solving lsys->systemSolve() of createGeometry of meshCompound of GFace::mesh, as shown in Figure 2, but this should not be the direct cause, I looked at the I've looked at the whole mesh generation process of gmsh, before 2D mesh generation, 1D mesh information is needed, for the model in the add-on during 1D mesh generation, the number and position of the nodes and line meshes of the mesh of my compiled version of gmsh are the same as those of the exe version of the official website of gmsh, but in the process of generating the 2D mesh, no matter which mesh algorithm is used, the mesh will be initial mesh, I have compared the compiled version with the exe version of gmsh, and I have found the error in lsys->systemSolve().
compared the compiled version with the official website's exe version of the initial mesh, and found that there are not small differences between the two, in order to facilitate the display, I use a surface of the EADS Mako_HEAT.stp model (saved in EADS Mako_HEAT-face.stp) to generate the initial mesh as a demonstration, and Fig. 2 demonstrates the official website's exe version Figure 3 shows the exe version from the official website, and Figure 4 shows my compiled version.
I tried many versions of opencascade and many versions of gmsh source code, but I can't avoid this problem. The exe version that can be used directly from the official website produces the same results, and the set compound operation handles the model without any model that can't generate a mesh. I suspect that it may be a problem with my gmsh compilation, and I may not have turned on a certain option. The main configuration of my gmsh source code is shown in Figure 5.
Thank you for taking time to read this issues. I look forward to hearing from you soon. EADS_Mako_HEAT.geo