From: Zhu Zihao <all_but_last@163.com>
To: guile-devel@gnu.org
Subject: Make the pkgconfig file of Guile relocatable.
Date: Mon, 28 Feb 2022 00:04:52 +0800 [thread overview]
Message-ID: <86tuckqoge.fsf@163.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]
Currently, the guile-3.0.pc.in in 'meta' use the variable substitution
directly.
prefix=@prefix@
exec_prefix=@exec_prefix@
bindir=@bindir@
libdir=@libdir@
includedir=@includedir@
datarootdir=@datarootdir@
datadir=@datadir@
pkgdatadir=@datadir@/guile
pkgincludedir=@includedir@/guile
sitedir=@sitedir@
extensiondir=@libdir@/guile/@GUILE_EFFECTIVE_VERSION@/extensions
siteccachedir=@libdir@/guile/@GUILE_EFFECTIVE_VERSION@/site-ccache
libguileinterface=@LIBGUILE_INTERFACE@
sitedir, siteccachedir and extensiondir will be subsituted to the full
path of the install path of Guile.
But sometimes I want to install guile module in different
prefix(e.g. NixOS, Guix, flatpak). I have to adjust these variable
manually.
My idea is change the definition of sitedir, siteccachedir, extensiondir
use the variable substition of pkg-config instead of autotools.
For example
sitedir=${datadir}/guile/site/@GUILE_EFFECTIVE_VERSION@
siteccachedir=${libdir}/guile/@GUILE_EFFECTIVE_VERSION@/extensions
....
So I can use
pkg-config guile-3.0 --define-variable=libdir=$MY_PREFIX --variable=siteccachedir
to get the correct install directory.
Thoughts?
--
Retrieve my PGP public key:
gpg --recv-keys D47A9C8B2AE3905B563D9135BE42B352A9F6821F
Zihao
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]
next reply other threads:[~2022-02-27 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 16:04 Zhu Zihao [this message]
2022-02-28 7:03 ` Make the pkgconfig file of Guile relocatable Nala Ginrut
2022-10-12 12:25 ` 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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86tuckqoge.fsf@163.com \
--to=all_but_last@163.com \
--cc=guile-devel@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.
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).