Re: Building an X86 binary with Visual Studio Community 2013
Vin Shelton <[email protected]>
| Newsgroups | gmane.emacs.xemacs.beta |
|---|---|
| Message-ID | <CACeGjnW7KfM8TH=BMKCcN8VLxJ_0cjVrsqKdGqg315nMGBXv+Q@mail.gmail.com> |
Dear Biswajit, On Sun, May 31, 2015 at 3:52 PM, Biswajit Khandai <[email protected]> wrote: > > Vin, > This is where my original comment of "the build will fail in a heartbeat" had come from. > > I thought this time around you or someone might work with me if I wanted to give it an initial spin. Is that (or not) the case ? > > I wonder : Is xemacs still a serious and live project ? If it is, is Window native binary considered a serious enough part of the project ? (I've copied xemacs-beta as that is the medium for communication among the XEmacs developers and maybe someone else will want to chime in.) I don't really understand your points; I'll explain the situation as I see it: 1. I am currently making Windows installation kits. Those kits are built with VS6. The Windows Installation kits, at least in part thanks to your prodding/encouragement, are an ongoing activity. I generally create a new installation kit with each update to the 21.5 development branch. 2. If someone else wants to build Windows Installation kits using a different version of Visual Studio (or a different toolchain altogether), he or she is welcome to work through the issues necessary. I am happy to advise/help in that effort, but I do not currently have a copy of VS2012 or VS2013, so my advise will be somewhat theoretical in nature. You (or whoever else wants to take this on) will have to roll up your sleeves and struggle with various issues (manifest files among them). Whether or not XEmacs is serious and alive, is, IMO, in the eye of the beholder. Thanks for the bug report on paren highlighting. Since you narrowed the failure down to the menu, I will take a look at that. - Vin