From: Alex Kost <alezost@gmail.com>
To: guile-devel@gnu.org
Subject: Re: Maybe missing features on guild
Date: Sat, 24 Dec 2016 00:29:48 +0300 [thread overview]
Message-ID: <87lgv6s59v.fsf@gmail.com> (raw)
In-Reply-To: <87twav8xk4.fsf@fimbulvetr.bsc.es> ("Lluís Vilanova"'s message of "Fri, 25 Nov 2016 15:05:15 +0100")
Lluís Vilanova (2016-11-25 15:05 +0100) wrote:
> Hi guiler crowd!
>
> I have a project that uses guile as a scripting system, and want to provide both
> the scm sources and compiled go files as part of the installation.
>
> But I've found the following issues (using guile 2.1.4):
>
> * Argument --load-path for "guild compile" sets %load-path, but not
> %load-compiled-path. AFAIU, loading a .go dependency instead of a .scm one
> might make compilation slightly faster.
I also think "-C/--load-compiled-path" is a missing feature of "guild
compile". As a workaround, I call guild like this:
GUILE_LOAD_COMPILED_PATH=... guild compile ...
--
Alex
prev parent reply other threads:[~2016-12-23 21:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 14:05 Maybe missing features on guild Lluís Vilanova
2016-12-23 21:29 ` Alex Kost [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=87lgv6s59v.fsf@gmail.com \
--to=alezost@gmail.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).