From: Helmut Eller <eller.helmut@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: The 'cross' directory
Date: Tue, 15 Aug 2023 10:05:45 +0200 [thread overview]
Message-ID: <m2y1icu3vq.fsf@gmail.com> (raw)
In-Reply-To: <83pm3rcxh7.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 13 Aug 2023 08:39:16 +0300")
On Sun, Aug 13 2023, Eli Zaretskii wrote:
>> From: Richard Stallman <rms@gnu.org>
>> So I think it should have worked to make `temacs' cross-compiling
>> and then run the rest on the target machine. That should have been
>> easy because it did not need to compile or link any C code.
>
> This should still work, although I doubt if anyone tried it lately.
> Emacs with native-compilation cannot be built that way, because the
> native-code *.eln files are produced at build time, and cannot be
> included in the tarball (they depend on the architecture of the target
> machine and include signatures of the Emacs binary and the location of
> the source *.el files). But Emacs without native-compilation could be
> produced in such two steps, except that the target environment still
> needs some support tools: GNU Make, cp and rm. (Alternatively, they
> could invoke the final build commands by hand, if they know how.)
Is it possible/easy to cross-compile Emacs for Windows on a Unix
machine? Possibly with the help of Wine for dumping.
Debian has a package gcc-mingw-w64-x86-64, so I suppose installing the
cross compiler itself is fairly easy.
Helmut
next prev parent reply other threads:[~2023-08-15 8:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 17:09 The 'cross' directory Eli Zaretskii
2023-08-08 0:51 ` Po Lu
2023-08-09 3:47 ` Richard Stallman
2023-08-09 3:54 ` Po Lu
2023-08-13 1:43 ` Richard Stallman
2023-08-13 2:10 ` Po Lu
2023-08-13 2:14 ` Emanuel Berg
2023-08-13 5:39 ` Eli Zaretskii
2023-08-15 8:05 ` Helmut Eller [this message]
2023-08-15 11:44 ` Eli Zaretskii
2023-08-16 21:32 ` Helmut Eller
2023-08-17 7:44 ` Eli Zaretskii
2023-08-17 18:52 ` Helmut Eller
2023-08-15 9:45 ` Richard Stallman
2023-08-10 2:15 ` Richard Stallman
2023-08-10 16:37 ` Jose E. Marchesi
2023-08-10 17:01 ` [External] : " Drew Adams
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=m2y1icu3vq.fsf@gmail.com \
--to=eller.helmut@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--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 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).