We offered the option to link a custom built tetgen library to ug4 for quite some time. This was rather tedious and prone to error.
We also offer tools/tetgen which may be installed through ughub. The latter just builds an executable which may be used from commandline or e.g. by the ProMesh application (not the plugin).
With this merge request I removed the first option and instead included an option LINK_TETGEN which is offered by tools/tetgen.
To use it, install tetgen using ughub, enable the tool in cmake and also enable LINK_TETGEN in cmake:
Part of this merge request is also a bit of cleanup to link libraries to targets in a more specific way.
Finally, also part of this merge request is a fix for builds with VisualStudio on Windows: Binaries are now written to ug4/bin directly instead of ug4/bin/Release or ug4/bin/Debug.
We offered the option to link a custom built tetgen library to ug4 for quite some time. This was rather tedious and prone to error. We also offer
tools/tetgenwhich may be installed throughughub. The latter just builds an executable which may be used from commandline or e.g. by the ProMesh application (not the plugin).With this merge request I removed the first option and instead included an option
LINK_TETGENwhich is offered bytools/tetgen.To use it, install tetgen using ughub, enable the tool in cmake and also enable LINK_TETGEN in cmake:
Part of this merge request is also a bit of cleanup to link libraries to targets in a more specific way.
Finally, also part of this merge request is a fix for builds with VisualStudio on Windows: Binaries are now written to ug4/bin directly instead of ug4/bin/Release or ug4/bin/Debug.