From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: emacs-devel@gnu.org
Subject: Re: WINDRES
Date: Mon, 01 Apr 2013 13:36:18 +0300 [thread overview]
Message-ID: <83k3om35ct.fsf@gnu.org> (raw)
In-Reply-To: <51595AA5.8050403@dancol.org>
> Date: Mon, 01 Apr 2013 11:00:05 +0100
> From: Daniel Colascione <dancol@dancol.org>
> CC: emacs-devel@gnu.org
>
> On 4/1/13 10:37 AM, Eli Zaretskii wrote:
> > The windres tool is looked up by the configure.ac using
> > AC_CHECK_TOOL. Shouldn't that be AC_CHECK_TARGET_TOOL instead, to
> > better support cross-compilation?
>
> That would be a fine change, but I haven't tested cross-compilation
> of the cygw32 build at all, I'm not sure whether it works at all.
Even if cross-compilation currently doesn't work (and I'm not sure
either way), I think there's no harm removing one obstacle on its way.
> Is there any particular reason you're wondering about windres right
> now?
I'm modifying the Emacs Posix configury to be able to produce the
MinGW build. As a side effect, I'm reading the docs of every autoconf
macro that I didn't use before (which is quite a lot ;-), to make sure
I understand what I'm doing. In this case, I was surprised to see
AC_CHECK_TOOL instead of AC_CHECK_PROG, so I looked it up.
I will wait for autoconf experts here to chime in, before making the
change to use AC_CHECK_TARGET_TOOL on the trunk.
next prev parent reply other threads:[~2013-04-01 10:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 9:37 WINDRES Eli Zaretskii
2013-04-01 10:00 ` WINDRES Daniel Colascione
2013-04-01 10:36 ` Eli Zaretskii [this message]
2013-04-01 10:30 ` WINDRES Andreas Schwab
2013-04-01 11:53 ` WINDRES Eli Zaretskii
2013-04-01 12:54 ` WINDRES Andreas Schwab
2013-04-01 13:36 ` WINDRES Eli Zaretskii
2013-04-01 15:18 ` WINDRES Dmitry Antipov
2013-04-01 16:23 ` WINDRES Eli Zaretskii
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=83k3om35ct.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dancol@dancol.org \
--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).