Per Stephen's request, I'm forwarding this to xemacs-beta. - Vin ---------- Forwarded message ---------- From: <turnbull(a)sk.tsukuba.ac.jp&gt; Date: Sat, Nov 8, 2014 at 2:25 AM Subject: Re: [P21.5] Patches for Native Windows Builds To: "It's me FKtPp ;)" <kai.fktpp(a)gmail.com&gt; Cc: Vin Shelton <acs(a)alumni.princeton.edu&gt;, Michael Sperber <sperber(a)deinprogramm.de&gt; Hi all! We should move this conversation to xemacs-beta. [I'm not doing it and in fact removed xemacs-patches because my employer's POP3 server is down and I'm replying from squirrely-mail, and can't change From to my subscribed address, and on top of that I'm having connectivity issues with mail.xemacs.org so won't be able to approve it in the spamtrap! Feel free to forward or just quote in a post to -beta as appropriate. Gaaahh.] There's an excellent description of GNU Emacs's mingw/msys build system at http://bzr.savannah.gnu.org/lh/emacs/trunk/annotate/head:/nt/INSTALL If possible we should be compatible with that for obvious reasons, and for not so obvious reasons -- namely, Stallman is finally coming around on the issue of loadable modules. My understanding from the Python guys is that managing them is easy enough on *nix or Mac OS X because everybody agrees on ABIs on each platform, but it's a world of pain on Windows because of DLL hell compounded by at least three mutually incompatible ABIs: MSVC, mingw, and mingw64. (Don't take "ABI" too seriously, the issue is more which version of msvcrt.dll is used or something like that, but I just use ABI as an abbreviation.) The main thing missing from that documentation is the 32bit/64bit issue. My understanding from the Python discussion I mentioned elsewhere is that there are current two mingw projects: the dormant "mainline" mingw (implied -32) project, and the more active but more beta mingw64 project. I'm not sure which is preferred for GNU Emacs. "Somebody" should ask Eli Zaretskii <eliz(a)gnu.org&gt; about it. I'd do it (Eli and I go way back), but really somebody directly involved in the Windows dev work for XEmacs ought to get to know him, and I can't promise to get involved in that, I've got too much other stuff I've promised to do already. > I'd like to paticipate in the force if we chose the later way. Glad to hear that! > Thanks, > kai >> On Fri, Nov 7, 2014 at 7:54 PM, Vin Shelton <acs(a)alumni.princeton.edu&gt; >> wrote: >> > This "auto-migrate" thing sounds cool. Too bad you didn't work in the >> > compiler or tools groups at Microsoft. If you like I can put you in touch with Steve Dower at MSFT, who's helping the Python crew with their migration issues. >> But don't hold your breath. :-) Nope.:-) But with fresh blood interested in helping, something should get done in a reasonable time frame, I think! Steve _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta