unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: HiPhish <hiphish@posteo.de>
To: guile-user@gnu.org
Subject: Make a library installable?
Date: Sun, 12 May 2019 16:50:28 +0200	[thread overview]
Message-ID: <6372591.9J7NaK4W3v@aleksandar-ixtreme-m5740> (raw)

Hello Schemers,

A while ago I presented my MessagePack implementation for Guile[1] here and I 
want to make it available to users. Guile has no dedicated package manager, so 
it's either manual or Guix, and I would like to support both. What it the best 
way of doing it?

So far I have a repository that can be used right away with Guile by adding 
its path to the load path. This is handy for testing and working where I just 
just invoke Guile as `guile -L .`. For more permanent installation I have a 
makefile, it "builds" everything into `./build` (i.e. inside the repo) and from 
there the user could copy-paste the files into the desired directory.

I was thinking of adding an "install" target to the makefile which would copy 
the directory structure of `./build` to the directory given by `$PREFIX`. The 
user could then type

    make lib doc && make PREFIX=/usr/local install

to get everything installed globally. A package manager like Guix could  just 
specify a different `PREFIX`.

Is this reasonable? And where exactly should the Guile code be placed? I have 

	$(PREFIX)/share/guile/site/$(guile_ver)/msgpack

as the directory for now. The value of `$guile_ver` is determined 
automatically at build time:

	guile_ver = $(shell $(GUILE) -c '(display (effective-version))')

This would only make the module available for Guile 2.2, no other version. Is 
there a better directory?

I guess I could use GNU Autotools instead of a manually written makefile, but I 
would rather stick to what I know and is simple for such a simple project.

[1] https://gitlab.com/HiPhish/guile-msgpack





             reply	other threads:[~2019-05-12 14:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-12 14:50 HiPhish [this message]
2019-05-12 20:18 ` Make a library installable? → conf Arne Babenhauserheide
2019-05-12 20:50   ` Arne Babenhauserheide
2019-05-12 22:23 ` Make a library installable? amirouche
2019-05-13 22:22   ` HiPhish
2019-05-14 10:57     ` Amirouche Boubekki
2019-05-15 17:31 ` Catonano

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=6372591.9J7NaK4W3v@aleksandar-ixtreme-m5740 \
    --to=hiphish@posteo.de \
    --cc=guile-user@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).