From: Paul Eggert <eggert@cs.ucla.edu>
To: David Michael <fedora.dm0@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Cross-compiling
Date: Wed, 5 Feb 2020 13:13:40 -0800 [thread overview]
Message-ID: <6eb264a1-a197-7d1e-8b18-dc1b4feb6ebc@cs.ucla.edu> (raw)
In-Reply-To: <87r1z9hwcj.fsf@gmail.com>
On 2/5/20 7:45 AM, David Michael wrote:
> Does anyone familiar with the build process see problems with this? Is
> it something that would be acceptable upstream?
Something along those lines should be acceptable, I'd think.
I assume you're building from a tarball, and not from Git. If you are
building from Git, then the first step should be to build a tarball
natively, and then start from the tarball. This should simply any
cross-build support we need to add.
make-docfile shouldn't be needed native, as we can distribute its output
as part of the tarball.
For blessmail, we can convert it to a shell script on platforms that
have a shell (which should be the only platforms where cross-building is
an issue.) Blessmail is obsolete anyway - perhaps we should start
installing blessmail only on explicit request - but I digress.
For make-fingerprint, it's not that important and we could make its use
optional. Or we could write a shell script a la blessmail. Or we could
convert it from C to Elisp and integrate it as part of the build
process. Either way, we wouldn't need to build it on the build host.
If we do the above, we wouldn't need to worry so much about native vs
cross-builds.
prev parent reply other threads:[~2020-02-05 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 15:45 Cross-compiling David Michael
2020-02-05 21:13 ` Paul Eggert [this message]
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=6eb264a1-a197-7d1e-8b18-dc1b4feb6ebc@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=fedora.dm0@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.