From: Eli Zaretskii <eliz@gnu.org>
To: Helmut Eller <eller.helmut@gmail.com>
Cc: rms@gnu.org, luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: The 'cross' directory
Date: Thu, 17 Aug 2023 10:44:20 +0300 [thread overview]
Message-ID: <834jky6rl7.fsf@gnu.org> (raw)
In-Reply-To: <m25y5er7up.fsf@gmail.com> (message from Helmut Eller on Wed, 16 Aug 2023 23:32:46 +0200)
> From: Helmut Eller <eller.helmut@gmail.com>
> Cc: rms@gnu.org, luangruo@yahoo.com, emacs-devel@gnu.org
> Date: Wed, 16 Aug 2023 23:32:46 +0200
>
> On Tue, Aug 15 2023, Eli Zaretskii wrote:
>
> >> From: Helmut Eller <eller.helmut@gmail.com>
> >> Is it possible/easy to cross-compile Emacs for Windows on a Unix
> >> machine? Possibly with the help of Wine for dumping.
> >
> > Maybe, I don't know. I never tried, and neither I think has anyone
> > else.
>
> I tried it now. It kinda works, but it's not easy. What follows is a
> summary of the steps that I did, for the unlikely case that somebody is
> interested in these things:
Thanks. The use of Posix configury for building Emacs for Windows was
designed and tested only for native (host = target) builds, and was
never tested otherwise, so some hidden assumptions and other similar
issues are not surprising.
> 4. Executing "make" now wants to execute make-docfile.exe, but can't.
I believe this is not a Windows specific issue.
> 6. Now "make RUN_TEMACS=$(pwd)/src/wine-temacs.sh" wants run bootstrap-emacs
> to produce all the .elc files.
Only if you build from Git. If you build from the release tarball,
all the *.elc files are supposed to be already present in the tree.
> 8. Even with all the .elc files in place, make still wants to execute
> bootstrap-emacs for things like
>
> GEN ../lisp/leim/quail/CCDOSPY.el
> or
> GEN ../../lisp/cedet/semantic/bovine/c-by.el
> or
> ELC ../lisp/loaddefs.elc
>
> I just waited and let it proceed, as I didn't know any shortcuts.
Why is this a problem? If it runs on the host (which it should),
that's okay. If it runs only after Emacs was dumped, that's indeed a
problem, but again: in a release tarball all those *.elc files should
already be present.
next prev parent reply other threads:[~2023-08-17 7:44 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
2023-08-15 11:44 ` Eli Zaretskii
2023-08-16 21:32 ` Helmut Eller
2023-08-17 7:44 ` Eli Zaretskii [this message]
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=834jky6rl7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eller.helmut@gmail.com \
--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).