From: Richard Stallman <rms@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: larsi@gnus.org, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: GStreamer xwidget
Date: Tue, 23 Nov 2021 01:11:39 -0500 [thread overview]
Message-ID: <E1mpP1n-0003YD-UN@fencepost.gnu.org> (raw)
In-Reply-To: <8735noajkl.fsf@yahoo.com> (message from Po Lu on Mon, 22 Nov 2021 12:41:14 +0800)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> > If so, does selecting gst-plugins-good statically link _all_ of the
> > free plugins? If not that, then what?
> Asking for gst-plugins-base and gst-plugins-good will result in
> GStreamer dynamically linking with the free plugins. As long as Emacs C
> code doesn't explictly tell GStreamer to load the ugly or bad plugins,
> which are non-free, GStreamer will never load them.
This sounds mostly good, but this worries me:
> > Does the choice of one of those inevitably have to be made when
> > building Emacs?
> No, see below.
I don't see any specifics about that point, and it is an important point.
Can you please show me precisely how Emacs would specify which plugins
to load? What are the specifications of the interface?
What does the code actually look like? If it uses any macros,
what does it macroexpand into?
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2021-11-23 6:11 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ee7cq2mu.fsf.ref@yahoo.com>
2021-11-19 2:51 ` GStreamer xwidget Po Lu
2021-11-19 4:01 ` T.V Raman
2021-11-19 4:21 ` Po Lu
2021-11-19 5:38 ` Lars Ingebrigtsen
2021-11-19 5:49 ` Po Lu
2021-11-19 6:19 ` Lars Ingebrigtsen
2021-11-19 6:37 ` Po Lu
2021-11-19 6:53 ` Lars Ingebrigtsen
2021-11-19 13:03 ` Eli Zaretskii
2021-11-19 13:07 ` Po Lu
2021-11-19 13:22 ` Eli Zaretskii
2021-11-19 13:33 ` Po Lu
2021-11-19 13:45 ` Eli Zaretskii
2021-11-20 5:07 ` Po Lu
2021-11-20 7:23 ` Eli Zaretskii
2021-11-20 7:27 ` Po Lu
2021-11-21 5:19 ` Richard Stallman
2021-11-21 6:53 ` Lars Ingebrigtsen
2021-11-22 4:31 ` Richard Stallman
2021-11-20 7:42 ` Richard Stallman
2021-11-20 8:05 ` Po Lu
2021-11-20 8:16 ` Lars Ingebrigtsen
2021-11-21 5:18 ` Richard Stallman
2021-11-21 5:27 ` Po Lu
2021-11-22 4:31 ` Richard Stallman
2021-11-22 4:41 ` Po Lu
2021-11-23 6:11 ` Richard Stallman [this message]
2021-11-23 7:07 ` Po Lu
2021-11-23 20:54 ` Richard Stallman
2021-11-24 0:32 ` Po Lu
2021-11-25 5:32 ` Richard Stallman
2021-11-25 8:13 ` Po Lu
2021-11-25 11:34 ` Alexandre Garreau
2021-11-27 4:09 ` Richard Stallman
2021-12-01 12:30 ` Dmitry Gutov
2021-12-01 17:53 ` Arthur Miller
2021-12-02 0:51 ` Po Lu
2021-12-02 2:47 ` chad
2021-11-27 4:08 ` Richard Stallman
2021-11-27 4:38 ` Po Lu
2021-11-28 4:24 ` Richard Stallman
2021-11-28 4:42 ` Po Lu
2021-11-28 8:04 ` Yuri Khan
2021-11-28 8:16 ` Po Lu
2021-11-29 3:02 ` Richard Stallman
2021-11-29 7:31 ` Yuri Khan
2021-11-29 7:44 ` Po Lu
2021-11-29 21:12 ` Richard Stallman
2021-11-30 1:38 ` Po Lu
2021-11-30 8:30 ` Yasushi SHOJI
2021-11-30 9:29 ` Po Lu
2021-11-30 10:30 ` Yasushi SHOJI
2021-12-01 7:04 ` Richard Stallman
2021-12-01 7:09 ` Po Lu
2021-11-30 4:09 ` Richard Stallman
2021-11-29 3:01 ` Richard Stallman
2021-11-29 3:12 ` Po Lu
2021-11-30 4:09 ` Richard Stallman
2021-11-30 4:36 ` Po Lu
2021-12-01 7:04 ` Richard Stallman
2021-11-23 6:11 ` Richard Stallman
2021-11-23 6:55 ` Po Lu
2021-11-24 4:28 ` Richard Stallman
2021-11-21 6:52 ` Lars Ingebrigtsen
2021-11-21 14:45 ` Arthur Miller
2021-11-23 6:09 ` Richard Stallman
2021-11-22 4:31 ` Richard Stallman
2021-12-01 7:07 ` Richard Stallman
2021-12-01 7:31 ` Po Lu
2021-12-01 8:30 ` Alexandre Garreau
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1mpP1n-0003YD-UN@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).