Package Details: meshlab 2022.02-1

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.027588
First Submitted: 2020-09-18 22:35 (UTC)
Last Updated: 2022-11-03 12:35 (UTC)

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 to cmake 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 and patches to github.com/AUR-meshlab

Latest Comments

1 2 3 4 5 6 .. 13 Next › Last »

frankspace commented on 2022-11-08 02:35 (UTC)

This needs to have the "git: allow 'file' protocol" changes from the meshlab-git package applied. Beyond that, however, why does this depend on openssl-1.0 specifically? I've tested it, and it seems to compile (in a chroot) and run just fine with the current openssl 3.0.7 installed. I have no clue what it even needs ssl for, but it does successfully check for updates. Openssl 1.0 is end-of-life'd, and unless there is some reason why meshlab specifically needs an obsolete version, may I respectfully suggest considering dropping that in favor of regular openssl?

mosgerila commented on 2022-01-05 09:44 (UTC)

Need update. Current version is 2021.10

bartus commented on 2021-08-26 07:04 (UTC) (edited on 2021-08-26 07:05 (UTC) by bartus)

@mahjong @winksaville: There's a simple trick to check if your home config files have any negative effect, run meshlab from console with altered $HOME e.g: HOME=/tmp/home meshlab 〜(￣▽￣〜)

wrvsrx commented on 2021-08-26 06:57 (UTC) (edited on 2021-08-26 07:06 (UTC) by wrvsrx)

I met the situation @mahjong said. But I fix by following method (I don't know which part solves the problem or why it works, but the white margin just disappears.)

Reboot. Log out from display. Connect to the PC by vnc (here white margin has disappeared). Log out from vnc. Remove kde config files. Log in to display.

I hope that can helps you.

mahjong commented on 2021-05-26 04:01 (UTC)

Does anyone else get that white area around mesh area (the area that has blue background)? https://imgur.com/6ZHMThA

Why am I getting it?

winksaville commented on 2020-07-02 23:19 (UTC)

I used pacman to install eigen: 


sudo pacman -Syu eigen

But, I was still getting an error that eigen3 was missing: 


$ makepkg -sir
==> Making package: meshlab 2020.06-1 (Thu 02 Jul 2020 01:16:09 PM PDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Installing missing dependencies...
error: target not found: eigen3
==> ERROR: 'pacman' failed to install missing dependencies.
==> Missing dependencies:
  -> eigen3
==> ERROR: Could not resolve all dependencies.

So I changed "eigen3" to "eigen" in "makedepends" to get it working: 


$ git diff PKGBUILD
diff --git a/PKGBUILD b/PKGBUILD
index 55b2e73..de27d91 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -8,7 +8,7 @@ arch=('i686' 'x86_64')
 url="http://www.meshlab.net"
 license=('GPL2')
 depends=('bzip2' 'glew' 'glu' 'openssl-1.0' 'qt5-base' 'qt5-declarative' 'qt5-script' 'qt5-xmlpatterns')
-makedepends=('cmake' 'eigen3' 'ninja' 'git' 'muparser' 'levmar' 'lib3ds' 'mpir')
+makedepends=('cmake' 'eigen' 'ninja' 'git' 'muparser' 'levmar' 'lib3ds' 'mpir')
 optdepends=('u3d: for U3D and IDTF file support'
             'lib3ds: for Autodesk`s 3D-Studio r3 and r4 .3DS file support'
             'levmar: for isoparametrization and mutualcorrs plugins'

bartus commented on 2020-06-08 14:58 (UTC) (edited on 2020-06-08 14:58 (UTC) by bartus)

@daren, I've made some adjustment to ninja call. But at the end I have to find a way to recreate options=(!makeflags) like behavior for ninja, as in contrast to make it starts nproc+2 build jobs by default where make starts single one...

ulidtko commented on 2020-06-08 10:50 (UTC)

Hey! Thanks for maintaining this.

Would you drop gcc10.patch from here? It doesn't apply anymore, since the upstream has already merged your GCC 10 fix.

disc-kuraudo commented on 2020-06-08 07:56 (UTC) (edited on 2020-06-08 07:56 (UTC) by disc-kuraudo)

Could you remove the MAKEFLAGS from the ninja line?

I put VERBOSE=1 in my MAKEFLAGS to see all the flags during compilation and this just breaks:

-- Build files have been written to: /build/meshlab/src/build
ninja: Entering directory `/build/meshlab/src/build'
ninja: error: unknown target 'VERBOSE=1'

Either edit the MAKEFLAGS before using it with make or don't mix it with this ninja shenanigans at all.

1 2 3 4 5 6 .. 13 Next › Last »