From: "Ben Key" <Bkey1@tampabay.rr.com>
Cc: <gnu-emacs-sources@gnu.org>, <emacs-devel@gnu.org>
Subject: RE: Patch for Windows implementation of play-sound
Date: Thu, 17 Oct 2002 23:31:21 -0400 [thread overview]
Message-ID: <001f01c27656$d45dd760$6401a8c0@GODDESS> (raw)
In-Reply-To: <20021016181608.CD18.LEKTU@terra.es>
I do have the newest MSSDK installed. Therefore, I am not getting the
warnings you are getting. However, if I do not define _WIN32_WINNT and
WINVER to be at least 0x0500 I get several compilation errors.
As for the section of emacs.c you mentioned, you a correct that that was an
unintentional change. Tomorrow I will create a new diff to resolve that
problem.
-----Original Message-----
From: Juanma Barranquero [mailto:lektu@terra.es]
Sent: Wednesday, October 16, 2002 12:34 PM
To: Bkey1@tampabay.rr.com
Cc: gnu-emacs-sources@gnu.org; emacs-devel@gnu.org
Subject: Re: Patch for Windows implementation of play-sound
On Wed, 16 Oct 2002 00:04:34 -0400, "Ben Key" <Bkey1@tampabay.rr.com> wrote:
> I have also tested this
> patch with Microsoft Visual C++ 6.0 and MinGW 2.0 / MSys 1.08.
Do you have a recent SDK from msdn.microsoft.com? The -DWINVER=0x0501
gives me about a gazillion of those:
> NOTE: WINVER has been defined as 0x0500 or greater which enables
> Windows NT 5.0 and Windows 98 features. When these headers were released,
> Windows NT 5.0 beta 1 and Windows 98 beta 2.1 were the current versions.
>
> For this release when WINVER is defined as 0x0500 or greater, you can only
> build beta or test applications. To build a retail application,
> set WINVER to 0x0400 or visit http://www.microsoft.com/msdn/sdk
> to see if retail Windows NT 5.0 or Windows 98 headers are available.
>
> See the SDK release notes for more information.
Also, is this bit from src/emacs.c intended, or did you cvs diff and
accidentally got this reversed?
> @@ -2302,13 +2302,11 @@
> doc: /* Non-nil means Emacs is running without interactive
terminal. */);
>
> DEFVAR_LISP ("kill-emacs-hook", &Vkill_emacs_hook,
> - doc: /* Hook to be run when kill-emacs is called.
> -Since `kill-emacs' may be invoked when the terminal is disconnected (or
> + doc: /* Hook to be run whenever kill-emacs is called.
> +Since kill-emacs may be invoked when the terminal is disconnected (or
> in other similar situations), functions placed on this hook should not
> expect to be able to interact with the user. To ask for confirmation,
> -see `kill-emacs-query-functions' instead.
> -
> -The hook is not run in batch mode, i.e., if `noninteractive' is non-nil.
*/);
> +see `kill-emacs-query-functions' instead. */);
> Vkill_emacs_hook = Qnil;
>
> empty_string = build_string ("");
/L/e/k/t/u
next prev parent reply other threads:[~2002-10-18 3:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 4:04 Patch for Windows implementation of play-sound Ben Key
2002-10-16 16:34 ` Juanma Barranquero
2002-10-18 3:31 ` Ben Key [this message]
2002-10-18 8:40 ` Juanma Barranquero
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='001f01c27656$d45dd760$6401a8c0@GODDESS' \
--to=bkey1@tampabay.rr.com \
--cc=emacs-devel@gnu.org \
--cc=gnu-emacs-sources@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).