When I use the compiled version and try to use the revolve mesh feature, it gives an error, but my folder contains the gmshcommon file. How should I resolve this?
Try this:
Compiling PrePoMax only creates some of its subfolders and default settings are prepared. To fully use a compiled version of PrePoMax, first look at the latest released version of the PrePoMax’s base folder. Then copy all folders that are missing in the compiled version from the released version (Models, NetGen, Solver…). Then you have to set the working folder and solvers (CalculiX) executables file name in the Settings->Calculix. In order to use the Gmsh mesher a file gmsh-4.12.dll must be copied from the release version lib subfolder to the compiled lib subfolder.
Especially the last point.
1 Like
The compiled version does not have a lib folder. Do I need to create one?
I think it wasn’t needed when I was compiling not so long ago, but perhaps it’s necessary now. I also had some compilation issues recently due to missing .dll files, also related to Gmsh. I ended up with Visual Studio running the last successful build.
How did you do it? I had created the lib folder and copied it over from the release version, but the same problem still occurred.
What I means is that I haven’t managed to fix the underlying issue yet so I just used the last successful build option in Visual Studio (it shows up when compilation fails due to missing files).
Are you using Visual Studio Code?
I recommend using Visual Studio Community 2026. In the build process, there is a command that should create a lib subfolder and then copy all .dll files into it. I am not sure how this functions in Visual Studio Code.
1 Like
I use Visual Studio 2022 Community. It used to work there so either something has changed or I made a mistake causing missing .dll files.
1 Like
I am also using Visual Studio Community 2026. May I ask how you did it?
You can try creating the corresponding folders where it prompts that they are missing, and then copy them over.
PrePoMax uses the NuGet package PrettyyBin, which should copy the DLL files from the root directory to the lib directory. It seems it does not work. I will dowload the code from the GitLab and try to reproduce the problem.
I did the following, and for me it works:
- download the code in .zip format and unzip it to a folder
- opened the solution file
- selected Debug → Start Debugging
The program starts, but since the settings file is missing, it throws an error. If you restart debugging, it will work since the settings file is created in the meantime. But I will fix this bug going forward.
A new folder should appear called /packages and inside it there should be PrettyBin.1.1.0 subfolder.
You can also try Build → Batch Build → Select All → Build, which will rebuild all projects.
1 Like
For me, neither regular compilation nor debugging run works. I do have the PrePoMax-master_5\packages\PrettyBin.1.1.0 folder with some contents, but there are still error messages about missing .dll files. I’ve tried it with a freshly downloaded repo, Kitware references readded and compilation submitted. I’ll try on another computer, maybe it’s something with my VS configuration.
1 Like
Any success with the compilation?
Somehow, I can compile only if I switch the configuration from Debug to Release. But I guess it’s good enough.
Did you try:
You can also try Build → Batch Build → Select All → Build, which will rebuild all projects.
1 Like
This gives me errors about missing .dll files:
Metadata file 'D:\PrePoMax_dev\PrePoMax-master_8\PrePoMax-master\GmshCommon\bin\x64\Debug\GmshCommon.dll' could not be found
Metadata file 'D:\PrePoMax_dev\PrePoMax-master_8\PrePoMax-master\CaeMesh\bin\x64\Debug\CaeMesh.dll' could not be found
Metadata file 'D:\PrePoMax_dev\PrePoMax-master_8\PrePoMax-master\GmshCommon\bin\x64\Debug\GmshCommon.dll' could not be found
Metadata file 'D:\PrePoMax_dev\PrePoMax-master_8\PrePoMax-master\CaeMesh\bin\x64\Debug\CaeMesh.dll' could not be found
Metadata file 'D:\PrePoMax_dev\PrePoMax-master_8\PrePoMax-master\GmshCommon\bin\x64\Debug\GmshCommon.dll' could not be found
Metadata file 'D:\PrePoMax_dev\PrePoMax-master_8\PrePoMax-master\vtkControl\bin\x64\Debug\vtkControl.dll' could not be found
Metadata file 'D:\PrePoMax_dev\PrePoMax-master_8\PrePoMax-master\CaeMesh\bin\x64\Debug\CaeMesh.dll' could not be found
Metadata file 'D:\PrePoMax_dev\PrePoMax-master_8\PrePoMax-master\vtkControl\bin\x64\Debug\vtkControl.dll' could not be found
Metadata file 'D:\PrePoMax_dev\PrePoMax-master_8\PrePoMax-master\CaeMesh\bin\x64\Debug\CaeMesh.dll' could not be found
Metadata file 'D:\PrePoMax_dev\PrePoMax-master_8\PrePoMax-master\CaeResults\bin\x64\Debug\CaeResults.dll' could not be found
Metadata file 'D:\PrePoMax_dev\PrePoMax-master_8\PrePoMax-master\vtkControl\bin\x64\Debug\vtkControl.dll' could not be found
Metadata file 'D:\PrePoMax_dev\PrePoMax-master_8\PrePoMax-master\CaeMesh\bin\x64\Debug\CaeMesh.dll' could not be found
Metadata file 'D:\PrePoMax_dev\PrePoMax-master_8\PrePoMax-master\CaeModel\bin\x64\Debug\CaeModel.dll' could not be found
Metadata file 'D:\PrePoMax_dev\PrePoMax-master_8\PrePoMax-master\CaeResults\bin\x64\Debug\CaeResults.dll' could not be found
Metadata file 'D:\PrePoMax_dev\PrePoMax-master_8\PrePoMax-master\CaeMesh\bin\x64\Debug\CaeMesh.dll' could not be found
Metadata file 'D:\PrePoMax_dev\PrePoMax-master_8\PrePoMax-master\CaeModel\bin\x64\Debug\CaeModel.dll' could not be found
Metadata file 'D:\PrePoMax_dev\PrePoMax-master_8\PrePoMax-master\CaeResults\bin\x64\Debug\CaeResults.dll' could not be found
Metadata file 'D:\PrePoMax_dev\PrePoMax-master_8\PrePoMax-master\UserControls\bin\Debug\UserControls.dll' could not be found
Metadata file 'D:\PrePoMax_dev\PrePoMax-master_8\PrePoMax-master\vtkControl\bin\x64\Debug\vtkControl.dll' could not be found
There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "D:\PrePoMax_dev\PrePoMax-master_8\PrePoMax-master\CaeGlobals\bin\x64\Debug\CaeGlobals.dll", "AMD64". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "D:\PrePoMax_dev\PrePoMax-master_8\PrePoMax-master\CaeJob\bin\x64\Debug\CaeJob.dll", "AMD64". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
Output Directory does not end with a trailing slash. This build instance will add the slash as it is required to allow proper evaluation of the Output Directory.
The build tools for v145 (Platform Toolset = 'v145') cannot be found. To build using the v145 build tools, please install v145 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution".
The build tools for v145 (Platform Toolset = 'v145') cannot be found. To build using the v145 build tools, please install v145 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution".
Maybe I missed some step. I just download and unzip the code, open the solution file in Visual Studio 2022, and recreate the Kitware references.
I am using Visual Studio 2026 and now I remember I retargeted the Project to a new C++ toolset, which is not available in Visual Studio 2022.
Please install Visual Studio 2026 with:
- Desktop development with C++
- C++/CLI support
- MSVC v145 build tools
- .NET Framework 4.8 targeting pack
Then open the solution, select Debug | x64, and run Clean Solution followed by Rebuild Solution.
The missing DLL errors are only a consequence of the failed C++ project compilation.
If this works, I will update the compilation instructions.
1 Like
