From: "Khuong D Pham" <xxx@xxx.com>
Subject: Re: Extending Emacs with C
Date: Tue, 11 Nov 2003 18:47:33 +0100 [thread overview]
Message-ID: <ud9sb.27798$jf4.1579491@news000.worldonline.dk> (raw)
In-Reply-To: 3fb08926$1@news.seqnet.net
How did you compile emacs with msvc6. I have tried it without success
I get this when I run nmake after execute configure.bat:
makefile (25): fatal error U1035: syntax error : expected ':' or '='
separator
"Siegfried Heintze" <siegfried@heintze.com> wrote in message
news:3fb08926$1@news.seqnet.net...
> I just compiled emacs on Win2000 using cl v12 (aka MSVC6). Hurray. Too bad
> it it does not link when using the latest Microsoft C compiler (v 13.1).
> Good thing I kept v12 around.
>
> Are there any documents that can guide me on extending emacs (elisp) with
C?
> I want to call some COM objects from elisp.
>
> Thanks,
> Siegfried
>
>
next prev parent reply other threads:[~2003-11-11 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-11 6:54 Extending Emacs with C Siegfried Heintze
2003-11-11 12:06 ` Gareth Rees
2003-11-11 18:13 ` Pascal Bourguignon
2003-11-11 17:47 ` Khuong D Pham [this message]
2003-11-12 2:19 ` Siegfried Heintze
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='ud9sb.27798$jf4.1579491@news000.worldonline.dk' \
--to=xxx@xxx.com \
/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.
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).