Re: [PATCH] check_writable for Win32 and cygwin repair
- First Post
- Replies
- Stats
-
Go to
- ----- 2024 -----
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2007 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2006 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2005 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2004 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2003 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2002 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2001 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2000 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 1999 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 1998 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
(Discussion re-directed to xemacs-beta - perhaps a few messages late.)
On 11/26/06, Benson Margulies <bim2006(a)basistech.com> wrote:
Set INCLUDE to point to the include directory of the SDK. You can do
this in the customize dialog box of visual studio, or in the
environment.
Once you do this, you can compile the versions I sent along in my
revised patch :-)
In other words, I seem to have confused two processes:
Process 1: Set INCLUDE to the platform SDK (and LIB, as well), and
compile the full version of my revised patch.
Process 2:
1- Regenerate QXE using my version of intl-encap-win32.c, and ignore
the platform SDK altogether.
2- build and test.
I'm recommending #1.
Yeah, I got the difference between #1 and #2. I'd like to keep option
#2 open if possible, which is why I sent along the diffs. BTW, I
couldn't get option #2 to work for me, but since you're going to issue
a revised patch, I wasn't going to sweat the details for the time
being.
- Vin
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Benson Margulies
Sunday, 26 November
Sun, 26 Nov
11:34 p.m.
New subject: [PATCH] check_writable for Win32 and cygwin repair
Hmm. I'll look at your diffs.
-----Original Message-----
From: ethersoft(a)gmail.com [mailto:ethersoft＠gmail.com] On Behalf Of Vin
Shelton
Sent: Sunday, November 26, 2006 6:00 PM
To: Benson Margulies
Cc: xemacs-beta(a)xemacs.org
Subject: Re: [PATCH] check_writable for Win32 and cygwin repair
(Discussion re-directed to xemacs-beta - perhaps a few messages late.)
On 11/26/06, Benson Margulies <bim2006(a)basistech.com> wrote:
Set INCLUDE to point to the include directory of the SDK. You can do
this in the customize dialog box of visual studio, or in the
environment.
Once you do this, you can compile the versions I sent along in my
revised patch :-)
In other words, I seem to have confused two processes:
Process 1: Set INCLUDE to the platform SDK (and LIB, as well), and
compile the full version of my revised patch.
Process 2:
1- Regenerate QXE using my version of intl-encap-win32.c, and ignore
the platform SDK altogether.
2- build and test.
I'm recommending #1.
Yeah, I got the difference between #1 and #2. I'd like to keep option
#2 open if possible, which is why I sent along the diffs. BTW, I
couldn't get option #2 to work for me, but since you're going to issue
a revised patch, I wasn't going to sweat the details for the time
being.
- Vin
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Benson Margulies
Sunday, 26 November
Sun, 26 Nov
11:51 p.m.
New subject: [PATCH] check_writable for Win32 and cygwin repair
Vin,
I'm disoriented.
My modified copy of intl-encap-win32.c adds:
file ACLAPI.h
yes GetNamedSecurityInfo
just above the 'file WINBASE.H'
Later, it changes a line to read:
split MessageBoxIndirect MSGBOXPARAMS NT 4.0+ only
This should cause the perl script to generate the qxe declaration for
GetNamedSecurityInfo.
The diffs you sent indicate, apparently, that the headers you have
aren't quite identical to those of the last person who ran the perl
script. But they don't show any spoor of GetNamedSecurityInfo.
If you used my intl-encap-win32.c as the input to the perl script and
nothing came out for GetNamedSecurityInfo, then I have no idea what's
going on.
Philosophical question: should we ALWAYS regenerate qxe as part of a
Windows build? Cygwin is a bit of neither fish now fowl, since cygwin
builders don't necessarily have VC anything, but they do build the qxe
files (against the GNU w32api files).
--benson
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
6373
days inactive
6373
days old
2 comments
2 participants
tags (0)
participants (2)
-
Benson Margulies -
Vin Shelton