From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "40492\\@debbugs.gnu.org" <40492@debbugs.gnu.org>
Subject: [bug#40492] [PATCH] gnu: Add meshlab
Date: Sat, 25 Apr 2020 19:47:03 +0000 [thread overview]
Message-ID: <qfq8UVmfNtFdXiGZfR8P0LMcbE1nU--Qmyi8V20fK1-BD-7D64nFJEJejMDgOF1HqSdBjbkKLzsrwh0Pfo0bVc27vtYP2e3t2eWEFK1xanI=@elenq.tech> (raw)
In-Reply-To: <87wo67ti07.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 817 bytes --]
Saluton!
> Egun on, :-)
>
> [...]
> Not really, I think CMake initially sets the RUNPATH to the build tree,
> as shown above, that’s OK. I think it changes it upon “make install”.
>
> > If I need to change that, what do I have to do?
>
> One way to fix it would be to arrange to pass ‘-Wl,-rpath,'$ORIGIN'’ on
> the link command line of the plugins.
>
> Another solution would be to add a post-install phase to move
> libmeshlab-common.so* to $output/lib, which seems more conventional,
> though perhaps upstream had good reasons not to do that.
Went for the second option because I didn't know how to make the first and
looks like it's working.
Also I think I fixed everything you pointed in the first comment.
I attach the updated patch.
Thanks for your help Ludo,
Ekaitz
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-gnu-Add-meshlab.patch --]
[-- Type: text/x-patch; name="0001-gnu-Add-meshlab.patch", Size: 2967 bytes --]
From 814e44cb90b1427a9af5d6a66392c5a39910e8fd Mon Sep 17 00:00:00 2001
From: Ekaitz Zarraga <ekaitz@elenq.tech>
Date: Tue, 7 Apr 2020 18:56:06 +0200
Subject: [PATCH] gnu: Add meshlab.
* gnu/packages/engineering.scm (meshlab): New variable.
---
gnu/packages/engineering.scm | 49 ++++++++++++++++++++++++++++++++++++
1 file changed, 49 insertions(+)
diff --git a/gnu/packages/engineering.scm b/gnu/packages/engineering.scm
index 5405db762c..dbe7faf78b 100644
--- a/gnu/packages/engineering.scm
+++ b/gnu/packages/engineering.scm
@@ -2491,3 +2491,52 @@ without any changes. And programmers that are familiar with the magellan API
can continue using it with a free library without the restrictions of the
official SDK.")
(license license:bsd-3)))
+
+(define-public meshlab
+ (let ((version "2020.04"))
+ (package
+ (name "meshlab")
+ (version version)
+ (source (origin
+ (method git-fetch)
+ (uri (git-reference
+ (url "https://github.com/cnr-isti-vclab/meshlab")
+ (commit (string-append "Meshlab-" version))
+ (recursive? #t)))
+ (sha256
+ (base32 "1vx9jcsnnxvzi90pcxpp7p72cqg3cm6jiivdmrxkzhr2fiz3pfvr"))))
+ (build-system cmake-build-system)
+ (native-inputs
+ `(("qtbase" ,qtbase)
+ ("qtscript" ,qtscript)
+ ("qtxmlpatterns" ,qtxmlpatterns)
+ ("mesa", mesa)
+ ("glu", glu)))
+ (arguments
+ `(#:tests? #f ; Has no tests
+ #:phases
+ (modify-phases
+ %standard-phases
+ (add-after
+ 'unpack 'go-to-source-dir
+ (lambda _ (chdir "src") #t))
+ (add-after
+ 'install 'move-files
+ (lambda* (#:key outputs #:allow-other-keys)
+ (let ((lib (string-append (assoc-ref outputs "out")
+ "/lib")))
+ (rename-file
+ (string-append lib "/meshlab/libmeshlab-common.so")
+ (string-append lib "/libmeshlab-common.so"))
+ #t))))))
+ (synopsis "3D triangular mesh processing and editing software")
+ (home-page "http://www.meshlab.net/")
+ (description "MeshLab is a system for the processing and
+editing of unstructured large 3D triangular meshes. It is aimed to help the
+processing of the typical not-so-small unstructured models arising in 3D
+scanning, providing a set of tools for editing, cleaning, healing, inspecting,
+rendering and converting this kind of meshes. These tools include MeshLab
+proper, a versatile program with a graphical user interface, and meshlabserver,
+a program that can perform mesh processing tasks in batch mode, without a
+GUI.")
+ (license license:gpl3+))))
--
2.26.1
next prev parent reply other threads:[~2020-04-25 19:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 17:08 [bug#40492] [PATCH] gnu: Add meshlab Ekaitz Zarraga
2020-04-22 17:23 ` Ludovic Courtès
2020-04-22 18:40 ` Ekaitz Zarraga
2020-04-22 19:52 ` Ludovic Courtès
2020-04-25 19:47 ` Ekaitz Zarraga [this message]
2020-04-26 20:49 ` Ludovic Courtès
2020-04-26 21:00 ` Ekaitz Zarraga
2020-04-27 8:03 ` Ludovic Courtès
2020-05-08 14:30 ` Ludovic Courtès
2020-05-08 14:30 ` Ludovic Courtès
2020-05-08 14:47 ` Ekaitz Zarraga
2020-05-10 21:29 ` Ekaitz Zarraga
2020-05-11 12:44 ` Ludovic Courtès
2020-05-11 14:10 ` Ekaitz Zarraga
2020-05-11 14:11 ` Ekaitz Zarraga
2020-05-14 8:06 ` Ludovic Courtès
2020-05-14 8:17 ` Ekaitz Zarraga
2020-05-15 22:41 ` Ekaitz Zarraga
2020-05-21 11:59 ` Ekaitz Zarraga
2020-06-12 16:13 ` Ludovic Courtès
2020-06-12 16:32 ` Ekaitz Zarraga
2020-06-12 19:45 ` Ludovic Courtès
2020-06-12 21:46 ` Ekaitz Zarraga
2020-06-13 14:58 ` bug#40492: " Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='qfq8UVmfNtFdXiGZfR8P0LMcbE1nU--Qmyi8V20fK1-BD-7D64nFJEJejMDgOF1HqSdBjbkKLzsrwh0Pfo0bVc27vtYP2e3t2eWEFK1xanI=@elenq.tech' \
--to=ekaitz@elenq.tech \
--cc=40492@debbugs.gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).