From: "Thompson, David" <dthompson2@worcester.edu>
To: alex@komputilo.eu
Cc: Andy Tai <atai@atai.org>, Guile User <guile-user@gnu.org>
Subject: Re: [EXT] Re: guile program distributed as single executable?
Date: Tue, 7 Jun 2022 08:02:41 -0400 [thread overview]
Message-ID: <CAJ=RwfZ6fP-Pf4N7H6QVO5_7+fum_ZW7+3LGT55K3sAgEbRJ8g@mail.gmail.com> (raw)
In-Reply-To: <87zgiq5cy8.fsf@komputilo.eu>
It doesn't actually generate standalone binaries. It is very hacky but it
can produce redistributable tarballs for a specific use-case (games using
chickadee) by including shared libraries and other bits from the host
system. Standalone executables will not really be possible until Guile's
compiler is capable of producing them.
- Dave
On Mon, Jun 6, 2022 at 9:32 AM Alex Sassmannshausen via General Guile
related discussions <guile-user@gnu.org> wrote:
> I think the last release of Guile Chickadee by DThompson (<
> https://dthompson.us/projects/chickadee.html>) provides a program that is
> supposed to generate standalone binaries (in the context of games).
>
> You may find either that program or insight from that program useful?
>
> Good luck,
>
> Alex
>
>
> Andy Tai <atai@atai.org> writes:
>
> > Hi, is there a way to “package” set of guile scripts, possibly with
> > other files like extensions, shared libraries, etc all combined into a
> > single executable? Something like PyInstaller for Python. Thanks for
> > info.
>
next prev parent reply other threads:[~2022-06-07 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 7:36 guile program distributed as single executable? Andy Tai
2022-06-06 9:58 ` Alex Sassmannshausen via General Guile related discussions
2022-06-07 12:02 ` Thompson, David [this message]
2022-06-07 14:12 ` [EXT] " james
2022-06-07 15:59 ` Olivier Dion via General Guile related discussions
2022-06-06 10:30 ` Arun Isaac
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='CAJ=RwfZ6fP-Pf4N7H6QVO5_7+fum_ZW7+3LGT55K3sAgEbRJ8g@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=alex@komputilo.eu \
--cc=atai@atai.org \
--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).