New site: https://github.com/cnr-isti-vclab/meshlab
New release v2016.12
Sorry for the delay in responding.
I am aware of the new version, however, it requires vcglib (https://github.com/cnr-isti-vclab/vcglib). I (or someone else) will have to port it.
I could probably port the dep but it hasn’t been updated since 2016, do we want to add what loooks like an abandoned project to update this one?
(In reply to Nathan from comment #2)
I created a review for a new port: devel/vcglib:
Keep in mind that I no longer maintain cad/meshlab. I still maintain other ports, however.
There is some activity on this project at the end of the year.
If no one takes it, I can try to get it back when version 2018 is released
I started to port the prerealese version of cad/meshlab. You can find my port on github https://github.com/lbartoletti/freebsd-ports/tree/meshlab/cad/meshlab
For the moment, it does not fully compile, but it is on the right track.
The problem is that you have to have devel/vcglib pointing to the development version and not to the latest release that is in our ports. See https://github.com/cnr-isti-vclab/meshlab/issues/258
Created attachment 203434 [details]
shar of meshlab
I made some patch on top of yours to manage the build of meshlab.
For now it build meshlab in the .build directory in work.
But for the moment the big issue is to have a correct pkg-plist, since
make makeplist cannot generate one. I guess that outsource building seems to add some issue.
At the end I am able to run meshlab from build directory in work/.build/distrib/ by adding to LD_LIBRARY_PATH work/.build/common since the libcommon library is build as shared library and openmesh link on it.
Note that I use a modified devel version of vcglib
Created attachment 203435 [details]
vcglib modification for meshlab
And here the patched version of vcglib used
(In reply to Thibault Payet from comment #8)
Sorry for the late. Thank you for updating this patch.
I tried with the latest version of meshlab and it builds.
I don't remember why I add outsource, maybe because there isn't a proper install script so it's easiest to find which files to install.
With or without outsource, you have to configure LD_LIBRARY_PATH until it's well instaled. I'll prepare an update next days