From: Po Lu <luangruo@yahoo.com>
To: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: svg library ideas
Date: Thu, 02 Feb 2023 13:18:04 +0800 [thread overview]
Message-ID: <87357oy7ar.fsf@yahoo.com> (raw)
In-Reply-To: <E1pNRki-0003Og-Qh@fencepost.gnu.org> (Richard Stallman's message of "Thu, 02 Feb 2023 00:03:16 -0500")
Richard Stallman <rms@gnu.org> writes:
> I think I understand. But if there is some usual set of settings that
> people would usually build Emacs with, maybe that could make prebuilt
> shared libraries start to be useful -- you just have to build them
> with that usual set of settings.
Indeed, but it would be difficult to build rsvg with that set of options
either.
The reason is apparently that the Rust compiler assumes newer Android
versions than what Emacs distributors will typically want to support.
Building anything with Rust also involves downloading a lot of binary
code off the internet, and I am not quite comfortable with that.
next prev parent reply other threads:[~2023-02-02 5:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87lelo15vw.fsf.ref@yahoo.com>
2023-01-27 13:09 ` svg library ideas Po Lu
2023-01-27 16:36 ` Jean Louis
2023-01-29 5:18 ` Richard Stallman
2023-01-29 5:29 ` Po Lu
2023-01-29 6:44 ` Jim Porter
2023-01-29 6:51 ` Eli Zaretskii
2023-01-31 4:19 ` Richard Stallman
2023-01-31 5:16 ` Po Lu
2023-02-02 5:03 ` Richard Stallman
2023-02-02 5:18 ` Po Lu [this message]
2023-02-03 0:19 ` Gregory Heytings
2023-01-29 6:43 ` Eli Zaretskii
2023-02-03 6:39 Pedro Andres Aranda Gutierrez
2023-02-03 8:00 ` Eli Zaretskii
2023-02-03 11:25 ` Jean Louis
2023-02-03 12:31 ` Po Lu
2023-02-03 13:37 ` Jean Louis
2023-02-03 12:42 ` Eli Zaretskii
2023-02-03 13:56 ` Yuri Khan
2023-02-04 7:06 ` Jean Louis
2023-02-04 8:49 ` Eli Zaretskii
2023-02-04 18:38 ` Jean Louis
2023-02-05 4:29 ` Richard Stallman
2023-02-04 7:07 ` Jean Louis
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87357oy7ar.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=emacs-devel@gnu.org \
--cc=rms@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.