From: Paul Emsley <paule@chem.gla.ac.uk>
Subject: Re: Packaging a guile-enabled binary
Date: 04 May 2004 13:07:34 +0100 [thread overview]
Message-ID: <1083672454.7480.41.camel@maybelline> (raw)
In-Reply-To: <20040502202152.73706.qmail@web14304.mail.yahoo.com>
On Sun, 2004-05-02 at 21:21, Mike Gran wrote:
> I'm putting together a little graphical program whose deliverable
> consists of a standard Linux binary (compiled C code) and a single
> Guile script. The binary is the main executable. The Guile script
> contains some configuration information, like a dot file, and some
> high-level functions that are called by the C code. The compiled
> binary requires the script to run successfully.
>
> Where's the best place for the Guile script? Best, in this case, means
> most foolproof for the the desktop user that is going to download the
> program as a pre-compiled package. Dot file? In the library? Is
> there a "right" way or a "standard"?
Presuming you are using GNU Autotools:
I'd use put them in $(pkgdatadir) or $(pkgdatadir)/scheme.
$(pkgdatadir) will expand to something like /usr/local/share/my-prog.
I'd give gcc the extra argument:
-DPKGDATADIR='"$(pkgdatadir)"'
so that you can use PKGDATADIR in your c code to (for example) stat the
scheme file (PKGDATADIR is just the directory, of course).
Paul.
p.s. GNU's not Linux.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2004-05-04 12:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-02 20:21 Packaging a guile-enabled binary Mike Gran
2004-05-02 20:52 ` Thamer Al-Harbash
2004-05-02 22:58 ` Mike Gran
2004-05-03 14:40 ` Linas Vepstas
2004-05-03 17:43 ` Mike Gran
2004-05-14 21:50 ` Rob Browning
2004-05-15 10:56 ` Marius Vollmer
2004-05-15 18:08 ` Rob Browning
2004-05-17 18:12 ` Marius Vollmer
2004-05-24 21:55 ` Marius Vollmer
2004-05-03 14:49 ` Linas Vepstas
2004-05-04 12:07 ` Paul Emsley [this message]
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=1083672454.7480.41.camel@maybelline \
--to=paule@chem.gla.ac.uk \
/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).