From: Sai Karthik <kskarthik@disroot.org>
To: Keith Wright <kwright@keithdiane.us>,
James Crake-Merani <james@jamescm.co.uk>
Cc: guile-user@gnu.org
Subject: Re: Option to create statically linked binaries
Date: Thu, 30 Dec 2021 11:58:23 +0530 [thread overview]
Message-ID: <3b8ccbfb-344c-05b1-9dc3-20b6a8497e1d@disroot.org> (raw)
In-Reply-To: <87ee5vi380.fsf@fcs22.keithdiane.us>
[-- Attachment #1.1.1: Type: text/plain, Size: 1023 bytes --]
Sorry for not able to phrase my thoughts into words properly. Yes, I
mean able to create native binaries out of guile programs, Just like how
in is done with Golang, where program binary includes go runtime & gc.
And, good to know that the team has it in on the roadmap & I personally
feel that it is a very good feature to have.
On 30/12/21 01:38, Keith Wright wrote:
> James Crake-Merani <james@jamescm.co.uk> writes:
>
>> On 21/12/29 10:59pm, Sai Karthik wrote:
>>> Hello everyone! I'm new to guile. I am exploring the language since a couple
>>> of days. It would be nice to have option to produce such binaries for
>>> programs built using guile (like with golang & some more langs).
>
>> I'm not sure what you're referring to when you say 'such binaries'.
>
> I had the same confusion, until I noticed the header.
>
> Subject: Option to create statically linked binaries
>
> -- Keith
>
> PS: I think Dave has already answered: "No, not yeT".
--
https://kskarthik.gitlab.io/
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3185 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2021-12-30 6:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 17:29 Option to create statically linked binaries Sai Karthik
2021-12-29 19:27 ` James Crake-Merani
2021-12-29 20:08 ` Keith Wright
2021-12-30 6:28 ` Sai Karthik [this message]
2021-12-29 19:52 ` [EXT] " Thompson, David
2021-12-29 21:22 ` tomas
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=3b8ccbfb-344c-05b1-9dc3-20b6a8497e1d@disroot.org \
--to=kskarthik@disroot.org \
--cc=guile-user@gnu.org \
--cc=james@jamescm.co.uk \
--cc=kwright@keithdiane.us \
/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).