unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: Preprocessor defines in MS-Windows build
Date: Sun, 08 Jun 2008 09:36:16 +0300	[thread overview]
Message-ID: <u4p84mo0v.fsf@gnu.org> (raw)
In-Reply-To: <skvozts6.fsf@telefonica.net>

> From: =?iso-8859-1?Q?=D3scar_Fuentes?= <ofv@wanadoo.es>
> Date: Sun, 08 Jun 2008 01:53:29 +0200
> 
> Jason Rumney <jasonr@gnu.org> writes:
> 
> > 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?
> 
> I quick check for VC6 does not find i386. _X86_ is in WINDOWS.H

Sorry, I don't see any significance of this for MSVC.  Jason, are you
saying that compiling _any_ program with cl, the MS compiler,
_requires_ the -Di386 and -D_X86_ switches?  I don't think so.  If
not, then why do we need to tell cl it is compiling an x86 program? it
should know that by default.

Can someone with MSVC please see if removing these two switches causes
any trouble?

> >>  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.
> 
> CRTDLL.dll (?) is not on the list of loaded dll's for an Emacs
> process. MSVCRT.dll is.

Yes, so what do we need USE_CRT_DLL for, again?




  reply	other threads:[~2008-06-08  6:36 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
2008-06-07 23:53   ` Óscar Fuentes
2008-06-08  6:36     ` Eli Zaretskii [this message]
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=u4p84mo0v.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=ofv@wanadoo.es \
    /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).