Hi,
Here comes yet another status report from the project of converting to
GPLv3 or later.
There are two lists of files below. The first list contains all files
that are in an undecided state. Please inspect: Do we need to do anything
with them. If so what?
The second list contains all files that we can leave untouched and the
reason for that. Please inspect: Are all reasons OK and correct?
Are we getting close to the were an inspection of the xemacs-gplv3
repository could be performed? With the intent that it that is OK we
could merge back to trunk and go GPLv3 or later?
----------------------------------------------------------------------
"CHANGES-beta"
"ChangeLog"
"PROBLEMS"
"README"
"README.GPLv3"
"etc/ChangeLog"
"etc/Emacs.ad"
"etc/InstallGuide"
"etc/NEWS"
"etc/ONEWS"
"etc/OONEWS"
"etc/README"
"etc/editclient.sh"
"etc/emacskeys.sco"
"etc/emacsstrs.sco"
"etc/gtkrc"
"etc/package-index.LATEST.gpg"
"etc/sample.Xresources"
"etc/xemacs.1"
"lib-src/ChangeLog"
"lib-src/README"
"lisp/ChangeLog"
"lisp/README"
"lisp/mule/mule-locale.txt"
"man/ChangeLog"
"man/README"
"modules/ChangeLog"
"modules/base64/Makefile"
"modules/common/configure-post.ac"
"modules/common/configure-pre.ac"
"modules/zlib/Makefile"
"nt/ChangeLog"
"nt/Emacs.ad.h"
"nt/Installation.el"
"nt/README"
"nt/Win32.cf"
"nt/lisp.ico"
"nt/site.def"
"nt/xemacs.dsp"
"nt/xemacs.dsw"
"src/ChangeLog"
"src/README"
"src/README.kkcc"
"src/m/README"
"src/s/README"
"src/s/freebsd.h"
"src/s/irix6-0.h"
"src/s/netbsd.h"
"src/s/sol2.h"
"tests/ChangeLog"
"tests/Dnd/README"
"tests/automated/README"
"version.sh.in"
----------------------------------------------------------------------
These files below are the files that we might be able to leave as
they are. The reason for why they need not to be changed is listed
after each file: (Some reasons are taken verbatim from private
communication or the "GPL version 3 source survey")
----------------------------------------------------------------------
"INSTALL" -> old FSF Documentation license
"config.guess" -> Part of config which is still GPLv2 or later. See "http://savannah.gnu.org/projects/config"
"config.sub" -> Part of config which is still GPLv2 or later. See "http://savannah.gnu.org/projects/config"
"etc/ETAGS.ChangeLog" -> BSD and GPL v2 or later
"etc/VEGETABLES" -> Not copyrightable.
"etc/XKeysymDB" -> MIT
"etc/ctags.1" -> Part of the etags distribution, which is not part of XEmacs.
"etc/custom/example-themes/ex-custom-file" -> Generated(!?) or GPL V2 or later?
"etc/etags.1" -> Part of the etags distribution, which is not part of XEmacs.
"etc/gnuattach.1" -> simple man link to gnuserv.1
"etc/gnuclient.1" -> simple man link to gnuserv.1
"etc/gnudoit.1" -> simple man link to gnuserv.1
"etc/refcard.ps.gz" -> Generated from refcard..tex
"etc/sample.Xdefaults" -> It is deprecated, so it can be removed but is only a three line reference to .Xresources
"etc/xemacs-X.ico" -> GPLv2 or later but there is not meta data for the file where this can be documented.
"info/dir" -> Generated(?)
"install-sh" -> MIT-style "no advertising" license
"lib-src/b2m.c" -> This is the version from GNU Emacs, so should be OK.
"lib-src/config.values.in" -> Generated.
"lib-src/emacs.csh" -> I don't think this even works with XEmacs ("emacsclient"), so I believe we can just delete it.
"lib-src/insert-data-in-exec.c" -> Compatible license.
"lib-src/mmencode.c" -> Compatible license.
"lisp/dump-paths.el" -> Empty file. Not copyrightable.
"lisp/term/bobcat.el" -> Emacs version has no explicit license declaration
"lisp/term/vt102.el" -> Emacs version has no explicit license declaration
"lisp/term/vt125.el" -> Emacs version has no explicit license declaration
"lisp/term/vt200.el" -> Emacs version has no explicit license declaration
"lisp/term/vt201.el" -> Emacs version has no explicit license declaration
"lisp/term/vt220.el" -> Emacs version has no explicit license declaration
"lisp/term/vt240.el" -> Emacs version has no explicit license declaration
"lisp/term/vt300.el" -> Emacs version has no explicit license declaration
"lisp/term/vt320.el" -> Emacs version has no explicit license declaration
"lisp/term/vt400.el" -> Emacs version has no explicit license declaration
"lisp/term/vt420.el" -> Emacs version has no explicit license declaration
"lock/.precious" -> Not copyrightable.
"modules/canna/install-sh" -> MIT
"modules/ldap/install-sh" -> MIT
"modules/postgresql/install-sh" -> MIT
"modules/sample/external/install-sh" -> MIT
"modules/sample/internal/install-sh" -> MIT
"move-if-change" -> Identical to GPLv3 or later Emacs version
"nt/Xmd.patch" -> GPLv2 or later but only a few lines
"nt/file.ico" -> MIT
"nt/minitar.c" -> Public domain
"nt/paths.h" -> Generated
"nt/xemacs.ico" -> GPLv2 or later but there is not meta data for the file where this can be documented.
"src/alloca.c" -> Public domain.
"src/depend" -> Generated
"src/emacs-marshals.c" -> Generated.
"src/emacs-widget-accessors.c" -> Generated.
"src/intl-auto-encap-win32.c" -> Generated.
"src/intl-auto-encap-win32.h" -> Generated.
"src/libsst.c" -> Compatible license.
"src/libsst.h" -> Compatible license.
"src/libst.h" -> Compatible copyright.
"src/linuxplay.c" -> Compatible license. (MIT-like)
"src/miscplay.c" -> Compatible license. (MIT-like)
"src/miscplay.h" -> Compatible license. (MIT-like)
"src/nas.c" -> Compatible license. (MIT-like)
"src/paths.h.in" -> Generated.
"src/s/openbsd.h" -> Too short. (< 10 lines)
"src/s/usg5-4-2.h" -> Too short. (< 10 lines)
"src/sunplay.c" -> Compatible copyright.
"tests/gtk/UNIMPLEMENTED" -> Does notes need a license?
"tests/tooltalk/beeps.el" -> Too short. (< 10 lines)
----------------------------------------------------------------------
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Dear XEmacs Developers,
I recently got a large roundtuit dropped in my lap (my startup company
imploded), so I've spent a few days working on XEmacs native Windows
setup kits.
On Fri, Oct 31, 2014 at 8:45 PM, Biswajit Khandai <b_khandai(a)yahoo.com> wrote:
> I was assuming that the stable channel native windows binary will be built
> by "someone".... If that assumption is right, then the same "someone" could
> build the beta channel native windows binary. It may not be you,
> necessarily.
Your assumption is correct, but I am the only someone who builds these
kits. I will try to make a setup kit for every release, but it is
difficult for me to know how much time I will have for making setup
kits in between releases.
> However, if that assumption is wrong, I would like you to know that a heck
> of a lot of people use xemacs on Windows - maybe you underestimate the
> number of such people.
Dear Biswajit - thank you for your kind words. They certainly made me
feel like my efforts in this area have been well worthwhile.
I have re-made setup kits for 21.4.22, 21.5.34 and 21.4 latest and
21.5 latest. I will upload them this afternoon to ftp.xemacs.org.
I will be sending a small patch to XEmacs-patches to work around a
couple of difficulties building without TLS on native Windows. I have
not attempted to build with TLS as of yet.
- Vin
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hi, Henry!
Thanks for your efforts on this. I have copied xemacs-beta on my reply.
On Sun, Mar 29, 2015 at 9:52 PM, Henry S. Thompson <ht(a)inf.ed.ac.uk> wrote:
> OK, small progress. Using VS6:
>
> Adding the following to syswindows.h at around line 605, in the
> _non_-CYGWIN_HEADERS branch
>
> typedef int WINBOOL;
> typedef intptr_t LONG_PTR;
> typedef uintptr_t ULONG_PTR;
> typedef uintptr_t DWORD_PTR;
> /* #define PCIDLIST_ABSOLUTE_ARRAY LPCITEMIDLIST *
> typedef const PCIDLIST_ABSOLUTE *PCIDLIST_ABSOLUTE_ARRAY;* */
> typedef LPCITEMIDLIST PCIDLIST_ABSOLUTE;
>
> allows several of the -msw.c files to compile.
>
> More similar work is required, I think.
>
> Oops: the last typedef above is wrong - I read the commented-lines above
> that backwards!
Thanks for making sure the native Windows build continues to work.
I appreciate your taking the lead on this, because I haven't made any
substantive progress on this over the weekend.
Here are a few comments:
1. I have checked in the configure changes, so please make your next
patchsets based off of current version control. Please split your
patchset into two patches: one containing the w32api refactoring /
unicode regeneration and a second one containing the 64-bit
(DEVICE_TYPE_) changes.
2. Back when I was looking at updating the unicode definitions, I had
a slightly different regexp in lib-sr/make-mswin-unicode.pl:
my $rettype_re = "(SHSTDAPI_\\(${tok_ch}+${ws_re}\\*?\\)|${tok_ch}" .
"[A-Za-z_0-9 \t\n\r\f]*?${tok_ch})";
I think this regexp is a little more restrictive than the one you
used, but I'm not sure that it makes a difference.
3. Here are my current definitions for the syswindows.h block:
#else /* !CYGWIN_HEADERS */
#define W32API_VER(major,minor) 0
#define W32API_INSTALLED_VER 0
/* Some types that show up in Cygwin headers but not in Visual Studio headers,
and cause problems if we used Cygwin headers to generate
intl-auto-encap-win32.[ch]. */
typedef LPCVOID PCVOID;
typedef int WINBOOL;
typedef intptr_t LONG_PTR;
typedef uintptr_t ULONG_PTR;
typedef uintptr_t DWORD_PTR;
typedef ITEMIDLIST ITEMIDLIST_ABSOLUTE;
typedef ITEMIDLIST_ABSOLUTE *PIDLIST_ABSOLUTE;
typedef const ITEMIDLIST_ABSOLUTE *PCIDLIST_ABSOLUTE;
/* Defined in w32api/winuser.h */
#define GCLP_MENUNAME (-8)
#define GCLP_HBRBACKGROUND (-10)
#define GCLP_HCURSOR (-12)
#define GCLP_HICON (-14)
#define GCLP_HMODULE (-16)
#define GCLP_WNDPROC (-24)
#define GCLP_HICONSM (-34)
#define GWLP_USERDATA (-21)
#define GWLP_WNDPROC (-4)
#define GWLP_HINSTANCE (-6)
#define GWLP_HWNDPARENT (-8)
#define GWLP_USERDATA (-21)
#define GWLP_ID (-12)
#define DWL_MSGRESULT 0
#define DWL_DLGPROC 4
#define DWL_USER 8
#ifdef _WIN64
#undef DWL_MSGRESULT
#undef DWL_DLGPROC
#undef DWL_USER
#endif
#define DWLP_MSGRESULT 0
#define DWLP_DLGPROC DWLP_MSGRESULT + sizeof(LRESULT)
#define DWLP_USER DWLP_DLGPROC + sizeof(DLGPROC)
#endif /* CYGWIN_HEADERS */
Not all of these definitions are necessary, but I think it's probably
best to include the entire GCLP/GWLP definition block.
Thanks for digging in on this.
-Vin
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hi Jerry --
I was just scrolling through tls.c and I saw the following:
/* Function that gathers passwords for PKCS #11 tokens. */
static char *
nss_pk11_password (PK11SlotInfo *slot, PRBool retry, void * UNUSED (arg))
{
[...]
lsp_password =
call1 (Qread_password, concat2 (prompt,
build_extstring (token_name, Qnative)));
c_password = LISP_STRING_TO_EXTERNAL (lsp_password, Qnative);
Our read-a-password function is called read-passwd, not read-password; I agree
the latter is a better name, was there another implementation you were using,
or was this just a mistake?
Best,
Aidan
--
‘Tramadol is further fed to cattle […] when working them […] (as draft
animals) so that the animals do not get tired quickly. …’
— Angewandte Chemie, Sept 2014, describing the social context of
(synthetic) tramadol having been found in Cameroon tree roots.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Adding the following to the !CYGWIN_HEADERS branch in syswindows.h
(around line 606) allows the main body of a VS6 compilation to work:
typedef int WINBOOL;
typedef intptr_t LONG_PTR;
typedef uintptr_t ULONG_PTR;
typedef uintptr_t DWORD_PTR;
#define PCIDLIST_ABSOLUTE LPCITEMIDLIST /* from /usr/include/w32api/shtypes.h */
#define GWLP_USERDATA (-21) /* the rest from /usr/include/w32api/winuser.h */
#define GCLP_HICON (-14)
#define GCLP_HCURSOR (-12)
#define GWLP_HINSTANCE (-6)
#define DWLP_DLGPROC DWLP_MSGRESULT + sizeof(LRESULT)
#define DWLP_MSGRESULT 0
#define DWLP_USER DWLP_DLGPROC + sizeof(DLGPROC)
but a different set of problems then kicks in as it tries to compile
intl-auto-encap-win32, which I haven't made any progress on yet.
ht
--
Henry S. Thompson, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht(a)inf.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/
[mail from me _always_ has a .sig like this -- mail without it is forged spam]
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
ACTIVITY SUMMARY (2015-03-24 - 2015-03-31)
XEmacs Issue Tracking System at http://tracker.xemacs.org/XEmacs/its/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
568 open ( +2) / 317 closed ( +0) / 885 total ( +2)
Open issues with patches: 13
Average duration of open issues: 2031 days.
Median duration of open issues: 2212 days.
Open Issues Breakdown
new 260 ( +2)
deferred 6 ( +0)
napping 3 ( +0)
verified 58 ( +0)
assigned 145 ( +0)
committed 19 ( +0)
documented 3 ( +0)
done/needs work 15 ( +0)
Issues Created Or Reopened (2)
______________________________
file-name-handler disabled in non-MULE XEmacs 2015-03-29
http://tracker.xemacs.org/XEmacs/its/issue886 created anonymous
info file build errors with texinfo 4.x 2015-03-29
http://tracker.xemacs.org/XEmacs/its/issue887 created anonymous
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Dear Henry et al,
Right off the bat I want to apologize for my tone in last night's
email. Yesterday was long and I was very tired when I wrote that.
Henry - thanks for your excellent work on getting a 64-bit XEmacs to
work on Cygwin! Yay!
On Fri, Mar 27, 2015 at 11:03 AM, Henry S. Thompson <ht(a)inf.ed.ac.uk> wrote:
> Vin Shelton writes:
>
>> First the good news - with your patches applied, I succeeded in building a
>> 64-bit cygwin XEmacs executable.
>
> Good news, yes, thanks for pressing ahead!
Thank you for all you have done.
>> Now the bad news - that patched XEmacs does not build under Windows native
>> (at least on the 32-bit XP VM I use for Native Windows kits).
>
> So, what compiler are you using at this point -- some MS compiler, or
> are we talking mingw here?
This is Visual Studio 6. Building with a newer version of VS will
require a whole 'nother set of work.
Mingw (either 32 or 64) remains a dream for the future - ideally we
could cross-compile using one of those compilers. Still dreaming.
:-)
>> After running the make-mswin-unicode.pl script, I get a bunch of
>> definitions that refer to WINBOOL, which is not a native Windows type.
>
> Hmm. I suspect a combination of my bad memory and unfamiliarity with
> the overall build architecture is to blame, but I didn't think your
> should have to run that at all, should you?
No, but I had compile difficulties building a Windows native (XP,
32-bit) executable with your new intl-auto-encap files, so I decided
to see if regenerating the intl-auto-encap files made a difference.
> If you did, it should be part of configure, right? I will have to try harder to understand the
> division of labour.
The Windows native build does not use configure. See nt/config.inc
and nt/xemacs.mak if you're curious (and you have a strong stomach -
MS nmake syntax is not for the weak).
In general, we could treat the intl-auto-encap files like configure -
we check them in, but people who are sufficiently interested should be
able to regenerate them. Prior to the most recent w32api changes, the
intl-auto-encap files had not been updated for years.
>
>> Here is the first such message:
>>
>> console-msw.c
>> C:\Cyg_opt\src\xemacs-21.5-2015-03-26\src\intl-auto-encap-win32.h(105) :
>> error C2146: syntax error : missing ';' before identifier
>> 'qxeSHGetNewLinkInfo'
>
> Can you send a copy of your intl-auto-encap-win32.h, so I can look at
> what is different?
Sorry if I misled you, but I don't think it makes any difference.
Using your intl-auto-encap-win32.h, here is what I see:
C:\Cyg_opt\src\xemacs-cygwin-test\nt>nmake -f xemacs.mak
Microsoft (R) Program Maintenance Utility Version 6.00.8168.0
Copyright (C) Microsoft Corp 1988-1998. All rights reserved.
1 file(s) copied.
'hg' is not recognized as an internal or external command,
operable program or batch file.
vcversion.c
WARNING: Compiling without dependency information.
Creating C:\Cyg_opt\src\xemacs-cygwin-test\lib-src\config.values
--------------------------------------------------------------------
OS version:
Microsoft Windows XP [Version 5.1.2600]
OS: Windows_NT
XEmacs 21.5-b34 "kale" configured for `i586-pc-win32'.
Building XEmacs using "NMAKE".
Building XEmacs using make flags " ".
Building XEmacs in source tree "C:\\Cyg_opt\\src\\xemacs-cygwin-test".
For src, using compiler "cl -nologo -W3 -DSTRICT -Zi -Od -MD -c -TP -IC:\Cyg
_opt\src\xemacs-cygwin-test\nt\inc -IC:\Cyg_opt\src\xemacs-cygwin-test\src -I"C
:/XEmacsBuild/lib\xpm-3.4k" -I"C:/XEmacsBuild/lib\xpm-3.4k\lib" -I"C:/XEmacsBuil
d/lib/giflib-4.1.6\include" -I"C:/XEmacsBuild/lib/libpng-1.2.46" -I"C:/XEmacsBui
ld/lib/zlib" -I"C:/XEmacsBuild/lib/tiff-3.9.5\libtiff" -I"C:/XEmacsBuild/lib\jpe
g-8c" -I"C:/XEmacsBuild/lib/zlib" -DHAVE_MS_WINDOWS -DHAVE_MENUBARS -DHAVE_SCRO
LLBARS -DHAVE_TOOLBARS -DHAVE_WIDGETS -DHAVE_DIALOGS -DHAVE_XPM -DFOR_MSW -DHAVE
_GIF -DHAVE_PNG -DHAVE_TIFF -DHAVE_JPEG -DHAVE_ZLIB -DHAVE_NATIVE_SOUND -DMULE -
DERROR_CHECK_ALL -DPDUMP -DSYSTEM_MALLOC -DDEBUG_XEMACS -D_DEBUG -DWIN32_LEAN_A
ND_MEAN -DWIN32_NATIVE -Demacs -DHAVE_CONFIG_H -DPATH_VERSION=\"21.5-b34\"
-DPATH_PROGNAME=\"xemacs\" -DEMACS_VERSION
=\"21.5-b34\" -DEMACS_PROGNAME=\"xemacs\" -DSHEBANG_PROGNAME=\"xemacs
-script\" -DSTACK_TRACE_EYE_CATCHER=xemacs_21_5_b34_i586_pc_win32 -DPATH_PREFIX=
\""c:\\Program Files\\XEmacs\\XEmacs-21.5-b34"\" -DEMACS_MAJOR_VERSION=21 -DEM
ACS_MINOR_VERSION=5 -DEMACS_BETA_VERSION=34 -DXEMACS_CODENAME=\""kale"\" -DX
EMACS_EXTRA_NAME=\"""\" -DPATH_LATE_PACKAGE_DIRECTORIES=\""C:/XEmacs"\" -DEMAC
S_CONFIGURATION=\"i586-pc-win32\"".
For lib-src, using compiler "cl -nologo -W3 -DSTRICT -Zi -Od -MD -IC:\Cyg_opt
\src\xemacs-cygwin-test\lib-src -IC:\Cyg_opt\src\xemacs-cygwin-test\src -DHAVE_C
ONFIG_H -DWIN32_NATIVE -DPATH_VERSION=\"21.5-b34\" -DPATH_PROGNAME
=\"xemacs\" -DEMACS_VERSION=\"21.5-b34\"
-DEMACS_PROGNAME=\"xemacs\" -DSHEBANG_PROGNAME=\"xemacs-script\" -DSTACK_TRACE_
EYE_CATCHER=xemacs_21_5_b34_i586_pc_win32".
Compiling as C++.
Installing XEmacs in "c:\\Program Files\\XEmacs\\XEmacs-21.5-b34".
Package path is "C:/XEmacs".
Compiling in support for Microsoft Windows native GUI.
Compiling in international (MULE) support.
Compiling in support for XPM images.
Compiling in support for GIF images.
Compiling in support for PNG images.
Compiling in support for TIFF images.
Compiling in support for JPEG images.
Compiling in support for GZIP compression/decompression.
Compiling in support for toolbars.
Compiling in support for dialogs.
Compiling in support for widgets.
Compiling in support for native sounds.
Using portable dumper.
Using system malloc.
Using DLL version of C runtime library.
Compiling in extra internal error-checking.
NOTE: ---------------------------------------------------------
NOTE: Compiling in support for runtime error-checking.
NOTE: XEmacs will run noticeably more slowly as a result.
NOTE: Error-checking is on by default for XEmacs beta releases.
NOTE: ---------------------------------------------------------
Compiling in debugging support (no slowdown).
--------------------------------------------------------------------
set COPYCMD=/y
1 file(s) copied.
set COPYCMD=/y
1 File(s) copied
set COPYCMD=/y
1 File(s) copied
make-dump-id.c
etags.c
getopt.c
getopt1.c
regex.c
Generating Code...
hexl.c
i.c
winclient.c
make-docfile.c
mmencode.c
movemail.c
pop.c
getopt.c
getopt1.c
regex.c
Generating Code...
sorted-doc.c
minitar.c
console-msw.c
C:\Cyg_opt\src\xemacs-cygwin-test\src\intl-auto-encap-win32.h(105) : error C2146
: syntax error : missing ';' before identifier 'qxeSHGetNewLinkInfo'
C:\Cyg_opt\src\xemacs-cygwin-test\src\intl-auto-encap-win32.h(105) : error C2501
: 'WINBOOL' : missing storage-class or type specifiers
C:\Cyg_opt\src\xemacs-cygwin-test\src\intl-auto-encap-win32.h(105) : fatal error
C1004: unexpected end of file found
NMAKE: fatal error U1077: 'cl' : return code '0x2'
Stop.
Thanks for thinking about this.
- Vin
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Henry -
First the good news - with your patches applied, I succeeded in building a
64-bit cygwin XEmacs executable.
Now the bad news - that patched XEmacs does not build under Windows native
(at least on the 32-bit XP VM I use for Native Windows kits). The problem,
as I know you suspect is the encapsulated unicode headers. Thanks for
taking on the challenge of fixing up our interface to the w32api, BTW, but,
as you know, it's a real bear.
After running the make-mswin-unicode.pl script, I get a bunch of
definitions that refer to WINBOOL, which is not a native Windows type.
Here is the first such message:
console-msw.c
C:\Cyg_opt\src\xemacs-21.5-2015-03-26\src\intl-auto-encap-win32.h(105) :
error C2146: syntax error : missing ';' before identifier
'qxeSHGetNewLinkInfo'
C:\Cyg_opt\src\xemacs-21.5-2015-03-26\src\intl-auto-encap-win32.h(105) :
error C2501: 'WINBOOL' : missing storage-class or type specifiers
C:\Cyg_opt\src\xemacs-21.5-2015-03-26\src\intl-auto-encap-win32.h(105) :
fatal error C1004: unexpected end of file found
NMAKE: fatal error U1077: 'cl' : return code '0x2'
I have tried 2 different approaches: defining WINBOOL and LONG_PTR and a
few others in syswindows.h. In hindsight, this was the more fruitful
approach, but not all the necessary source modules seem to include
syswindows.h (the details escape me at this exact moment).
My second and more braindead approach was to change each of the functions
like SHGetNewLinkInfo from "yes" to "review". I did this for probably 10
functions, but I didn't achieve joy (or a clean compile) and this is,
fundamentally not the right way to go.
Any thoughts on how to get the WINBOOL, etc types defined for the native
Windows build?
Thanks,
Vin
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta