Package Details: meshlab 2016.12-5

Git Clone URL: https://aur.archlinux.org/meshlab.git (read-only)
Package Base: meshlab
Description: System for processing and editing of unstructured 3D models arising in 3D scanning (qt5 version)
Upstream URL: http://www.meshlab.net
Keywords: 3d mesh pointcloud scan surface-reconstruction
Licenses: GPL2
Provides: meshlab
Submitter: net147
Maintainer: bartus (net147, dejavu)
Last Packager: bartus
Votes: 85
Popularity: 0.123742
First Submitted: 2009-10-04 10:58
Last Updated: 2017-06-21 12:54

Latest Comments

bartus commented on 2017-06-21 12:56

@chipbuster temporary fixed by removing unused functions from import_nvm,import_out.
tests{ Bundle (out) working, sfm (nvm) not tested. }

chipbuster commented on 2017-06-17 22:44

I seem to be getting a variant on the errors in the bug report at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853545, which are related to the effects of the GCC-7 compiler. Is this supposed to affect this package as well (I don't see any mentions of it)?

tjkopena commented on 2017-05-08 12:33

This package also currently has a dependency on openssl-1.0, which is not listed.

bartus commented on 2017-02-03 16:25

@dcanelhas
For meshlab_full.pro
\\ '-fopenmp' flags are included among applicable plugins *.pro files (will it make any difference to include it globaly? )

For external.pro
\\ enabling 'openmp' for ssynth could be beneficial (will test and update).

dcanelhas commented on 2017-01-31 11:05

if your cpu supports it i tmakes sense to change the PKGBUILD on the qmake lines to

qmake external.pro -r "QMAKE_CXXFLAGS_RELEASE+= -fopenmp" and "LIBS+=-fopenmp"
qmake meshlab_full.pro -r "QMAKE_CXXFLAGS_RELEASE+= -fopenmp" and "LIBS+=-fopenmp"

to avoid having gcc ignore all the
#pragma omp parallel for
and serializing the code that could be run in parallel on multiple cores

dejavu commented on 2017-01-11 02:29

Nice, thank you!

bartus commented on 2017-01-09 22:44

@dejavu
I made it ( dirty and hacky :) but seams to work, at least for me. Haven't been testing this solution extensively, bugs are expected. Please test and report if working fine for you.

bartus commented on 2017-01-07 14:38

@dejavu
Most of those are known issues ( io_txt and screedenpoisson already fixed in git ).
@net147
Works here on vbox and qemu.

dejavu commented on 2017-01-07 13:11

@bartus:
Oh, if some paths in the source code have to be patched/changed, than it would be more work than I have expected and probably it's not worth it?!
Another question, have you created the patches regarding "io_txt.pro" and the "cpp11_abs". It would be nice to report that upstream (GitHub), because that are trivial changes. I could also report it, if you are the author of those patches.
@net147:
I guess bartus can't do anything against that. It would be better to report it on GitHub ;-). I have also encountered the progress bar issue. It occurs only if it does not detect the video memory, starting it using my Intel card the bar remains, on my NVIDIA it shows the video memory.

net147 commented on 2017-01-07 11:01

@bartus
When I launch MeshLab, the graphics window shows as black. I have to go to File > New Empty Project and then close the project for it to display properly. Also, there is an indeterminate progress bar at the bottom right which keeps moving around left-to-right-to-left-to-right-etc.

This occurs on 2 systems - one with Intel graphics and one with software rendering in VirtualBox (export LIBGL_ALWAYS_SOFTWARE=1).

All comments