Henry S. Thompson writes:
Mats Lidell <matsl(a)xemacs.org> writes:
> Next thing will be to verify that I have a working native environment.
> Before summer it seems I installed VS2013. What do you think. Will
> that suffice as a test environment or do I need to go for the 2015
As always, you're a volunteer. It could be argued that *somebody* is
likely to have (or be stuck on) that environment for some reason (eg,
other software that requires image libs built in that environment).
If so, it would be helpful to have it installed.
It would probably be better if you could install VS2015, it was
painless (I unchecked _all_ the optional bits). There's clearly some
advantage in working in the same environment as we try to get things
working, as well as sharing with Python going forward. And VS2015
does seem to be what people will be loading if they start from
scratch. . .
Especially since the reports I have (already mentioned) are that
starting with VS2015 "native C APIs" in Windows will be fixed in stone
in some sense, and therefore it will be the preferred environment for
open source built on Windows.
XEmacs-Beta mailing list