From: "Ludovic Courtès" <ludo@gnu.org>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: How-to solve runpath-errors when splitting packages?
Date: Thu, 11 Apr 2019 10:48:22 +0200 [thread overview]
Message-ID: <87ftqp3p2h.fsf@gnu.org> (raw)
In-Reply-To: <2d6e4d33-3cdb-cf19-ce48-26aaebec763e@crazy-compilers.com> (Hartmut Goebel's message of "Tue, 5 Mar 2019 22:05:47 +0100")
Hi Hartmut,
Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:
> I already managed to split the output into several. Here is an the
> file-list for zbar:qt:
>
> /gnu/store/…-zbar-0.22-gtk/bin/zbarcam-gtk
> /gnu/store/…-zbar-0.22-gtk/lib/libzbargtk.so.0.0.2
> /gnu/store/…-zbar-0.22-gtk/lib/libzbargtk.a
> /gnu/store/…-zbar-0.22-gtk/lib/libzbargtk.la
> /gnu/store/…-zbar-0.22-gtk/include/zbar/zbargtk.h
> /gnu/store/…-zbar-0.22-gtk/lib/pkgconfig/zbar-gtk.pc
>
> Obviously zbarcam-gtk should use libzbargtk.so from the same output.
>
> How can I make zbarcam-gtk find the lib? Any ideas?
Normally, the build system (QMake I suppose?) should take care of it.
In GNU configure parlance, if you do:
./configure --libdir=/some/thing/lib
then the build system will ensure that executables, once installed, have
/some/thing/lib in their RUNPATH.
IOW, instead of adding a post-install phase that moves files around,
make sure to pass the right libdir option to QMake or whatever.
HTH!
Ludo’.
next prev parent reply other threads:[~2019-04-11 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 21:05 How-to solve runpath-errors when splitting packages? Hartmut Goebel
2019-04-11 8:48 ` Ludovic Courtès [this message]
2019-04-13 17:31 ` Timothy Sample
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=87ftqp3p2h.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.com \
/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).