unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Nala Ginrut <nalaginrut@gmail.com>
To: Matt Wette <mwette@alumni.caltech.edu>
Cc: guile-user@gnu.org
Subject: Re: request for help with module build/install
Date: Thu, 02 Jul 2015 11:12:58 +0800	[thread overview]
Message-ID: <1435806778.4336.53.camel@Renee-desktop.suse> (raw)
In-Reply-To: <4853AD2C-C8E3-4CD3-88B0-6823EC8A15B5@alumni.caltech.edu>

hi Matt!
For .scm files, you may put it to (%site-dir)
MOD_PATH := $(shell guile -c "(display (%site-dir))")

For compiled .go, you may put it to (%site-ccache-dir) here:
COMPILED_MOD := $(shell guile -c "(display (%site-ccache-dir))")

And it won't be compiled again when you load it.

Happy hacking!

On Wed, 2015-07-01 at 17:56 -0700, Matt Wette wrote:
> Hi Folks,
> 
> I have developed a set of guile modules.   I'd like to be able to generate a package hosted on, say, github.com (or any other recommended site).   Is there a document providing guidance for this task?   For example, looking at "%load-path" in guile I'm guessing I want the code to be installed in .../share/guile/2.0/site or .../share/guile/site.  Is the "site-dir" available as a variable?
> 
> Once installed, I'm guessing I can just use guild to compile and that will install the .go files in the right place (e.g.,  .../lib/guile/ccache/2.0).
> 
> Matt





  reply	other threads:[~2015-07-02  3:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02  0:56 request for help with module build/install Matt Wette
2015-07-02  3:12 ` Nala Ginrut [this message]
2015-07-05  2:19   ` Matt Wette
2015-07-05  8:42     ` Jan Wedekind
2015-07-05 13:05       ` Matt Wette
2015-07-05 13:44         ` Jan Wedekind
2015-07-02  7:01 ` Jan Wedekind
2015-07-02  8:04 ` Chaos Eternal
2015-07-02 13:08   ` Matt Wette

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=1435806778.4336.53.camel@Renee-desktop.suse \
    --to=nalaginrut@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=mwette@alumni.caltech.edu \
    /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).