Mats Lidell writes:
I agree. But why should the native build need to be broken in order
for the cygwin builds to work? Proper #ifdefs
May be prohibitively annoying to use because a lot of the *internal*
API stuff for Windows is automatically generated and needs to match up
with the system it's being build for, and other stuff is done by hand
in the makefile.inc or whatever it's called. Eventually we'll get
there, but *right now* things break.
If you want to work on the the "proper #ifdefs", that's another story,
but let's assume for now that Vin knows what's he's talking about and
Henry's quoting him accurately. If they want help, they'll explain.
Speaking of help, there's a Microsoft guy over on python-dev who's
doing a lot of work dragging Python's native build out of the dark
ages (up to VS 2015 or whatever, which he says, and fairly
convincingly says, means there won't be another C API break in MSFT
compilers in our lifetimes). Name is Steve Dower, if you don't know
him I'd be happy to provide an address or an introduction.
XEmacs-Beta mailing list