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