From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Preprocessor defines in MS-Windows build
Date: Sat, 07 Jun 2008 23:09:58 -0400 [thread overview]
Message-ID: <jwvwsl039u3.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <ufxrpm1qj.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 07 Jun 2008 23:25:24 +0300")
>> Ideally src/config.h, no (tho maybe it's more difficult)?
> You mean, nt/config.nt (that is copied into src/config.h), right?
I guess so.
> Why is that better, btw?
I just assume that the closer it is to the way other builds work
(i.e. autoconf in this case) the better.
>> > HAVE_NTGUI -- can be replaced with WINDOWSNT, since the W32
>> > build doesn't use any other GUI
>> Don't we support W32 builds without GUI?
> No, not AFAIK. The produced binary can be run with the -nw switch,
> but it has GUI support built in.
I see. But keeping a separate HAVE_NTGUI still makes sense in case we
want to allow non-GUI builds (or in case we ever want to provide an X11
version of the W32 build). It's not important to keep the distinction,
but I don't see much benefit in getting rid of rid.
>> > Does someone know anything that contradicts the above? If not, I
>> > think we should remove those defines that are not needed anymore, and
>> > put those which are needed in ms-w32.h.
>> Sounds fine to me,
> Thanks for the feedback.
My pleasure,
Stefan
next prev parent reply other threads:[~2008-06-08 3:09 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 [this message]
2008-06-07 21:57 ` Jason Rumney
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
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=jwvwsl039u3.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--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 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).