From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Bloat in Windows (revisited)
Date: Tue, 18 Jun 2019 13:59:51 -0400 [thread overview]
Message-ID: <jwvfto693r0.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 83wohisvpk.fsf@gnu.org
> That's right: any program that needs to be run as part of its build
> breaks cross-building, because cross-building produces binaries that
> cannot be run on the host where they are compiled.
Tho sometimes this can be fixed by building those tools twice:
- once for the target
- once for the host (to run it during the build).
E.g. I think we could build almost all of Emacs's files via
cross-compilation, the only exception being the dumped Emacs (i.e. the
.pdmp files): we could build a "host-temacs" which we can use to compile
the .elc files and then a "target-temacs" for the actual
intended target. But generating the target .pdmp file requires running
the target-temacs.
Stefan
next prev parent reply other threads:[~2019-06-18 17:59 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 [this message]
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
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
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=jwvfto693r0.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--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 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).