From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Bloat in Windows (revisited)
Date: Mon, 10 Jun 2019 11:52:55 +0300 [thread overview]
Message-ID: <2bd8b71e-cf67-32d0-7457-ecd6e5d05adc@gmail.com> (raw)
In-Reply-To: <874l53g0yk.fsf@russet.org.uk>
[-- Attachment #1: Type: text/plain, Size: 693 bytes --]
Hello, Phillip.
I was wondering about this bloat too. So the gist of my question is - do
we have to bundle dependencies with their optional stuff due to some
reason, like licensing requirements? For example do we really have to
bundle everything in Xpm-nox library distribution, or just the dll
itself would do, since for running we only need the dll?
Also, some time ago with manual testing I figured lists of dlls we need
get fully-fledged Emacs running for each toolchain, to use in a script.
See here
<https://github.com/sg2002/ms-windows-builder.el/blob/master/ms-windows-builder-config.el#L272>.
Maybe it's gonna help you in your quest.
--
Best Regards,
Nikolay Kudryavtsev
[-- Attachment #2: Type: text/html, Size: 1012 bytes --]
next prev parent reply other threads:[~2019-06-10 8:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 21:46 Bloat in Windows (revisited) Phillip Lord
2019-06-05 23:24 ` Tak Kunihiro
2019-06-06 14:29 ` Eli Zaretskii
2019-06-06 14:34 ` Stefan Monnier
2019-06-06 20:14 ` Phillip Lord
2019-06-07 2:07 ` Stefan Monnier
2019-06-09 21:16 ` Phillip Lord
2019-06-10 8:59 ` Nikolay Kudryavtsev
2019-06-10 12:17 ` Óscar Fuentes
2019-06-10 15:47 ` Nikolay Kudryavtsev
2019-06-10 21:28 ` Phillip Lord
2019-06-13 17:27 ` Nikolay Kudryavtsev
2019-06-13 17:53 ` Eli Zaretskii
2019-06-13 18:12 ` Nikolay Kudryavtsev
2019-06-13 21:34 ` Phillip Lord
2019-06-14 8:19 ` Nikolay Kudryavtsev
2019-06-17 15:59 ` Phillip Lord
2019-06-18 16:29 ` Eli Zaretskii
2019-06-18 17:59 ` Stefan Monnier
2019-06-18 19:27 ` Óscar Fuentes
2019-06-13 21:31 ` Phillip Lord
2019-06-07 6:08 ` Eli Zaretskii
2019-06-10 8:52 ` Nikolay Kudryavtsev [this message]
2019-06-10 15:27 ` Eli Zaretskii
2019-06-10 21:17 ` Phillip Lord
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=2bd8b71e-cf67-32d0-7457-ecd6e5d05adc@gmail.com \
--to=nikolay.kudryavtsev@gmail.com \
--cc=emacs-devel@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.