This package also currently has a dependency on openssl-1.0, which is not listed.
Search Criteria
Package Details: meshlab 2023.12-4
Package Actions
Git Clone URL: | https://aur.archlinux.org/meshlab.git (read-only, click to copy) |
---|---|
Package Base: | meshlab |
Description: | System for processing and editing of unstructured 3D models arising in 3D scanning (qt5 version) |
Upstream URL: | https://www.meshlab.net |
Licenses: | GPL2 |
Submitter: | bartus |
Maintainer: | bartus |
Last Packager: | bartus |
Votes: | 118 |
Popularity: | 0.28 |
First Submitted: | 2020-09-18 22:35 (UTC) |
Last Updated: | 2024-04-11 17:36 (UTC) |
Dependencies (26)
- bzip2 (bzip2-gitAUR)
- cgal (cgal-gitAUR)
- glew (glew-libepoxyAUR, glew-waylandAUR, glew-osmesa-gitAUR, glew-wayland-gitAUR, glew-gitAUR)
- glu (glu-gitAUR)
- gmp (gmp-hgAUR)
- mesa (mesa-minimal-gitAUR, mesa-gitAUR, mesa-wsl2-gitAUR, amdonly-gaming-mesa-gitAUR, mesa-amd-bc250AUR, mesa-amber)
- mpfr (mpfr-gitAUR)
- openssl (openssl-gitAUR, openssl-staticAUR)
- qhull
- qt5-base (qt5-base-gitAUR, qt5-base-headlessAUR)
- qt5-declarative (qt5-declarative-gitAUR)
- qt5-script (qt5-script-gitAUR)
- qt5-xmlpatterns (qt5-xmlpatterns-gitAUR)
- xerces-c
- boost (boost-gitAUR) (make)
- cmake (cmake-gitAUR) (make)
- eigen (eigen-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- lib3dsAUR (make)
- muparser (make)
- ninja (ninja-kitwareAUR, ninja-memAUR, ninja-fuchsia-gitAUR, ninja-gitAUR, ninja-jobserverAUR) (make)
- openctm-toolsAUR (make)
- patchelf (patchelf-gitAUR) (make)
- lib3dsAUR (optional) – for Autodesk`s 3D-Studio r3 and r4 .3DS file support
- muparser (optional) – for filer_func plugins
- openctm-toolsAUR (optional) – for compressed triangle mesh file format
Required by (0)
Sources (2)
Latest Comments
« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 15 Next › Last »
tjkopena commented on 2017-05-08 12:33 (UTC)
harrysummer commented on 2017-04-04 15:13 (UTC)
Crashing and digging for hours and finally solved...
For people who crashes under KDE environment when clicking on any filter and render menu items, please disable the automatic mnenomics generated by KDE. Maybe we should upstream this as a bug to the author of MeshLab?
Reference: http://stackoverflow.com/questions/32688153/how-to-disable-automatic-mnemonics-in-a-qt-application-on-kde
bartus commented on 2017-02-03 16:25 (UTC) (edited on 2017-02-03 16:29 (UTC) by bartus)
@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 (UTC)
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 (UTC)
Nice, thank you!
bartus commented on 2017-01-09 22:44 (UTC) (edited on 2017-01-10 09:04 (UTC) by bartus)
@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 (UTC) (edited on 2017-01-07 16:23 (UTC) by bartus)
@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 (UTC)
@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 (UTC) (edited on 2017-01-07 11:03 (UTC) by net147)
@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).
bartus commented on 2017-01-07 03:21 (UTC) (edited on 2017-01-07 03:26 (UTC) by bartus)
@dejavu
Saw fedora have meshlab in /usr (patched paths to shaders/plugins; should be working here to).
Pinned Comments
bartus commented on 2020-05-30 16:49 (UTC) (edited on 2020-05-30 16:49 (UTC) by bartus)
Some plugins (mainly render ones like SSAO) won't work with new cmake build system, will try to port
qmake
patches tocmake
and fix those.bartus commented on 2019-04-10 11:42 (UTC) (edited on 2021-08-26 06:58 (UTC) by bartus)
Please report
issues
andpatches
to github.com/AUR-meshlab