unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: dhruva <dhruvakm@gmail.com>
To: "Emacs Devel" <emacs-devel@gnu.org>
Subject: Build failure on M$ (using MSVC): Patch enclosed
Date: Tue, 20 May 2008 10:28:58 +0530	[thread overview]
Message-ID: <e3f230850805192158g166cf3f9yf1907631399635a2@mail.gmail.com> (raw)

Hi,
 The current HEAD does not build with MSVC compiler on M$ (XP). There
is still an issue with the emacs.ico file that this patch does not fix
(I just copy the emacs22.ico as emacs.ico to get my build). I will try
getting a working emacs using MSVC on M$ as IMO, debugging is much
easier using the M$ debugger than GDB on M$ platforms.

diff --git a/src/font.c b/src/font.c
index 4f75615..85eb615 100644
--- a/src/font.c
+++ b/src/font.c
@@ -22,7 +22,14 @@ along with GNU Emacs.  If not, see
<http://www.gnu.org/licenses/>.  */
 #include <config.h>
 #include <stdio.h>
 #include <stdlib.h>
+#ifdef WINDOWSNT
+#include <string.h>
+#ifndef strcasecmp
+#define strcasecmp(a,b) stricmp(a,b)
+#endif
+#else
 #include <strings.h>
+#endif
 #include <ctype.h>
 #ifdef HAVE_M17N_FLT
 #include <m17n-flt.h>
diff --git a/src/fontset.c b/src/fontset.c
index 82e5b4e..f3d17ea 100644
--- a/src/fontset.c
+++ b/src/fontset.c
@@ -66,6 +66,12 @@ along with GNU Emacs.  If not, see
<http://www.gnu.org/licenses/>.  */
 #define xassert(X)	(void) 0
 #endif	/* not FONTSET_DEBUG */

+#ifdef WINDOWSNT
+#ifndef strcasecmp
+#define strcasecmp(a,b) stricmp(a,b)
+#endif
+#endif
+
 EXFUN (Fclear_face_cache, 1);

 /* FONTSET

-dhruva

-- 
Contents reflect my personal views only!




             reply	other threads:[~2008-05-20  4:58 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20  4:58 dhruva [this message]
2008-05-20  6:10 ` Build failure on M$ (using MSVC): Patch enclosed dhruva
2008-05-20  8:26   ` dhruva
2008-05-20  8:58     ` dhruva
2008-05-20  9:46       ` Jason Rumney
2008-05-20 10:21         ` David Kastrup
2008-05-20 11:57           ` dhruva
2008-05-20 12:01             ` dhruva
2008-05-20 18:26       ` Eli Zaretskii
2008-05-20 12:11     ` Herbert Euler
2008-05-20 18:30       ` Eli Zaretskii
2008-05-20 18:12 ` Eli Zaretskii
2008-05-21  3:13   ` dhruva
2008-05-21 17:28     ` Stefan Monnier
2008-05-22  3:51       ` dhruva
2008-05-22  4:46         ` Stefan Monnier
2008-05-22  5:03           ` dhruva
2008-05-22  6:52             ` David Kastrup
2008-05-22  7:10               ` dhruva
2008-05-22  7:32                 ` David Kastrup
2008-05-22 15:49                 ` Stefan Monnier
2008-05-22 15:45               ` Stefan Monnier
2008-05-22  6:56             ` dhruva
2008-05-23  8:30               ` Eli Zaretskii
2008-05-23  9:15                 ` Jason Rumney
2008-05-22  8:32         ` Jason Rumney
2008-05-22  9:10           ` dhruva
2008-05-22  9:29             ` dhruva
2008-05-22 12:31               ` Jason Rumney
2008-05-22 13:10                 ` Jason Rumney
2008-05-22 13:33                   ` Miles Bader

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=e3f230850805192158g166cf3f9yf1907631399635a2@mail.gmail.com \
    --to=dhruvakm@gmail.com \
    --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).