On Thu, Apr 30, 2015 at 4:09 PM, Paul Moore <[email protected]> wrote: > Hi, > Who maintains the gcc package that's included in msys2? Is it handled > by the msys2 project, or elsewhere? There are specifically two > questions I want to ask:
All final package building and uploading is done by Alexey. The PKGBUILDs are maintained by the MSYS2 developers (with contributions from anyone submits a reasonable pull request). Changes and fixes for GCC are handled mostly by myself and Alexey. You can get a feel for who does what by using git blame in the PKGBUILDs by the way. > > 1. I see that gcc 5.1 is the latest version - how does that make its > way into msys2? (That's the minor question - I don't have any > particular need for a newer version of gcc) GCC 5.1 presents difficulty for us since the C++ ABI has changed (small string optimisation) which means we'd need to rebuild all C++ packages. Before we do that, I'd like to have a CI build system in place for that task. Also, 5.1 doesn't build correctly at the moment. > > 2. With the release of Visual C 2015, MS is releasing a new "Universal > CRT". It's not compatible with the older msvcrt, but it has the > advantage of being shipped as an OS component (directly with Windows > 10, and via windows update and vcredist for older versions). How would > support for the universal CRT get added to msys2/gcc? Who deals with > such things? (I'm not able to provide patches or anything like that, > I'd just like to know where to look to see if anyone was working on > this). This is the more major question for me, as I'd like to be able > to compile the xpm library (which needs a Unix-like build environment) > in a way that can be linked with MSVC 2015 (because I want to use that > to build vim, which uses xpm). I have workarounds (basically, don't > use xpm :-)) so it's not a critical issue, I just don't know a > "proper" fix other than mingw support for the universal CRT. MSYS2 supports Windows XP SP3 and above. Are you sure that XP SP3 will support this CRT? If not (and likely in any case also since want to depend only on stuff that comes with the OS) this would preclude us from switching to the MSVC 2015 Universal CRT. AFAIUI to provide binaries linked to that, we'd need to double up our repositories into legacy and universal variants which is a huge task. I don't understand why either xpm or vim need to be compiled with MSVC, can you explain that? Cheers, Ray. > > Thanks, > Paul > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > Msys2-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/msys2-users ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
