From: Kevin Ryde <user42@zip.com.au>
Cc: guile-user@gnu.org
Subject: Re: Where to install files?
Date: Tue, 11 Oct 2005 07:34:08 +1000 [thread overview]
Message-ID: <87wtkl6oq7.fsf@zip.com.au> (raw)
In-Reply-To: <87y851xja3.fsf@ossau.uklinux.net> (Neil Jerram's message of "Mon, 10 Oct 2005 20:29:40 +0100")
Neil Jerram <neil@ossau.uklinux.net> writes:
>
> Can someone tell me the Makefile.am incantations for determining where
> a package should install Scheme and Elisp files?
For the lisp bits, AM_PATH_LISPDIR in configure.ac then
dist_lisp_LISP = foo.el
or if you don't want it byte-compiled,
dist_lisp_DATA = foo-autoloads.el foo-devel.el
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2005-10-10 21:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 19:29 Where to install files? Neil Jerram
2005-10-10 21:34 ` Kevin Ryde [this message]
2005-10-10 22:54 ` Neil Jerram
2005-10-11 0:18 ` Greg Troxel
2005-10-11 18:42 ` Neil Jerram
2005-10-11 19:39 ` Greg Troxel
2005-10-13 18:08 ` Neil Jerram
2005-10-12 8:29 ` Ludovic Courtès
2005-10-13 18:19 ` Neil Jerram
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=87wtkl6oq7.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).