From: Sai Karthik <kskarthik@disroot.org>
To: guile-user@gnu.org
Subject: Option to create statically linked binaries
Date: Wed, 29 Dec 2021 22:59:29 +0530 [thread overview]
Message-ID: <4c029e88-d7ac-d294-a3dc-447b5be742b8@disroot.org> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 345 bytes --]
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).
Was this topic already discussed here before? Interested to know about
your thoughts.
--
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 reply other threads:[~2021-12-29 17:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 17:29 Sai Karthik [this message]
2021-12-29 19:27 ` Option to create statically linked binaries James Crake-Merani
2021-12-29 20:08 ` Keith Wright
2021-12-30 6:28 ` Sai Karthik
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=4c029e88-d7ac-d294-a3dc-447b5be742b8@disroot.org \
--to=kskarthik@disroot.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).