From: Jason Rumney <jasonr@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Preprocessor defines in MS-Windows build
Date: Sat, 07 Jun 2008 22:57:44 +0100 [thread overview]
Message-ID: <484B0458.7080604@gnu.org> (raw)
In-Reply-To: <uiqwlm9ud.fsf@gnu.org>
Eli Zaretskii wrote:
> _X86_ -- not needed, defined automatically by MinGW
> headers
> i386 -- not needed
>
They may not be needed for a mingw build, but do the msvc headers also
define them?
> HAVE_NTGUI -- can be replaced with WINDOWSNT, since the W32
> build doesn't use any other GUI
>
This is there so that theoretically users can build a smaller text only
Emacs. I have never heard of anyone doing so in the last ten years, and
would not be surprised if such a build fails, especially since the
multi-tty and unicode merges, so it may not be important. Perhaps it
should be added to the list of variables appended to src/config.h by
configure.bat to make it easier to test the text-only build.
> USE_CRT_DLL -- looks like it's unneeded, since we never use
> anything but the CRTDLL.dll runtime
>
I think there was at least an experimental attempt many years ago to use
MSVCRT.dll with the msvc compiler, and if we are ever to get more recent
versions of msvc working again it will be necessary to keep this around.
next prev parent reply other threads:[~2008-06-07 21:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-07 17:30 Preprocessor defines in MS-Windows build Eli Zaretskii
2008-06-07 19:04 ` Stefan Monnier
2008-06-07 20:25 ` Eli Zaretskii
2008-06-08 3:09 ` Stefan Monnier
2008-06-07 21:57 ` Jason Rumney [this message]
2008-06-07 23:53 ` Óscar Fuentes
2008-06-08 6:36 ` Eli Zaretskii
2008-06-09 1:55 ` David Robinow
2008-06-09 8:42 ` Eli Zaretskii
2008-06-26 22:47 ` Juanma Barranquero
2008-06-27 8:59 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=484B0458.7080604@gnu.org \
--to=jasonr@gnu.org \
--cc=eliz@gnu.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 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.