On 11/3/2016 11:17 AM, Kai Tietz wrote: > 2016-11-03 14:55 GMT+01:00 Óscar Fuentes <[email protected]>: >> Adrien Nader <[email protected]> writes: >> >>> Oh, just one thing: it probably makes more sense to simply state the >>> support becomes unoffcial for v6. It might work just as much as it might >>> not and the way to keep the support would be to speak up, provide some >>> input on the matter and tests. In other words, get actively involved. >> >> The policy suggested above is unsatisfactory for those who wish to see >> continuing XP support and for those who wish to replace the XP "cruft" >> with more efficient and convenient WIN32 APIs. >> >>> There are a couple big projects around (most notably Videolan and LO) >>> who likely might want to say a word about this. >> >> Good point. > > Indeed. > >> (FWIW: I'll like to see continuing XP support, but if it is a serious >> incovenience for you guys, I'll simply freeze on 5.x until the remaining >> XP machines die out.) > > Well, I think first step should be to set internal defines to Windows > Vista, and announce to the list that XP support is no longer explicit > maintained. > I am open minded to keep a XP for a while present, nevertheless we > shouldn't spend explicit efforts in this without need. If some of our > community are requesting to keep further XP support, we need some > volunteer to maintain it, or funds to our project for seeing a > reasoning.
Keeping what is already coded shouldn't be that difficult. The difficult part is testing changes with all variations of configuration. The statement could be stated that XP support has ceased testing the changes by the master maintainers. If you find an issue you are welcome to provide a patch solution with appropriate test to prove the break and fix. The test must be executed with more current API versions as well as the XP version. Maybe a branch just for XP that only changes for provable issues. Then the master branch doesn't need to worry about it. However, regardless of what we do here, the tools that use the API may move beyond XP. Those interested in XP need to ensure that the tool maintainers are also able to support it. So GCC (and other tool) maintenance for XP has ceased by the current maintainers, they don't have time to do both current and old API. -- Earnie ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
