From: phillip.lord@russet.org.uk (Phillip Lord)
To: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Bloat in Windows (revisited)
Date: Thu, 13 Jun 2019 22:31:52 +0100 [thread overview]
Message-ID: <877e9pxjcn.fsf@russet.org.uk> (raw)
In-Reply-To: <b91cf82a-7f53-3fe5-67e4-d3d35f09c1a5@gmail.com> (Nikolay Kudryavtsev's message of "Thu, 13 Jun 2019 20:27:25 +0300")
Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com> writes:
> Yes, so far it's windows only, but I'm definitely planning to get
> Linux to Windows cross-compilation working. And building sources
> too. You probably have some notes on doing those two things, would you
> be willing to share them with me?
Sure. The code is all in admin/nt/dist-build, as are the setup
instructions.
> Bootstraping is another thing I was planing to implement at some
> point, probably using Guile.
>
> Also Phillip, you you ever need any help with testing on Windows, feel
> free to email me directly. I'd probably be willing to help with that.
It's always good to get testing -- either of the releases or the
snapshots. I post about those here, first.
> Another thing I was thinking about in the long run, is turning that
> script into a more generic build tool, so that you could provide
> scripts for building not just Emacs, but other GNU and similar
> software. For example a script for Guile would be nice, since there's
> no official Windows distribution and then making plugins for different
> Unix package managers would be great.
A variation on my build scripts would do that, I think. Currently, I
just build out of source and then zip everything up. Most of it is not
emacs specific; with some fiddling, it would work for any autoconf'd
package.
At the end of the day, though, I think software like guile is probably
better support within an msys2 distribution with a package manager.
Phil
next prev parent reply other threads:[~2019-06-13 21:31 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 [this message]
2019-06-07 6:08 ` Eli Zaretskii
2019-06-10 8:52 ` Nikolay Kudryavtsev
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=877e9pxjcn.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=emacs-devel@gnu.org \
--cc=nikolay.kudryavtsev@gmail.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 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.