2015-05-26 10:57 GMT+02:00 Pavel Fedin <[email protected]>:
> Hello!
>
> > IMHO, no project is too small for a separate project page and
> repository. And I don't see how this could ever belong inside the mingw-w64
> project, honestly, as it is not related to the Windows runtime in any way
> (unless I'm missing something, which is very well possible).
>
> Is mingw-w64 strictly limited to compiler and runtime only? I thought
> it's not, i've seen some ported packages in "External binary packages" and
> "3rd party development tools". I thought portablexdr would perfectly fit
> there.
>
It has some useful additions in the area of tooling and low-level toolchain
libraries. Plus winpthreads, which is required for features of GCC and its
runtime libraries to function correctly.
The "External binary packages" was a haphazard attempt to set up something
like a package repository. It's a historical artifact and should be
removed. If anything, it has been completely superceded by the MSYS2
mingw-packages effort. That being said, all the packages there have their
source code available in a proper separate place, not anywhere near the
mingw-w64 source tree.
> > If you find Sourceforge too daunting, there's also the now more popular
> platform github, and numerous other alternatives where you can dump your
> source code. I believe that github will give it the greatest visibility
> though in the current open source world of hosting new projects.
>
> No, i don't. I would not like to set up a separate project only because
> the actual scope of portablexdr improvement is limited. There will be some
> bug fixes and code upgrades to fix warnings, but that's all. After this it
> will be frozen.
>
Hiding it in some other (mainly unrelated) project where it is not
distributed by default and can rot isn't any better. I have no say in
accepting the code or not, it just seems "out of scope" for a project
enabling GCC on Windows.
> > See also the MSYS2 packages for libvirt and portablexdr which you may
> consider contributing the changes to:
> > https://github.com/Alexpux/MINGW-packages/tree/master/mingw-w64-libvirt
> >
> https://github.com/Alexpux/MINGW-packages/tree/master/mingw-w64-portablexdr
>
> Ok, i can check with Alex about that. I just thought that gathering the
> complete set of various tools and useful packages (like MinGW32 and Cygwin
> projects do) is a good idea.
>
That's exactly what the MSYS2 project does. Mingw-w64 itself currently does
not do this, and for a long time, didn't even provide "official builds".
Now of course there are official builds, but the 3rd party libraries
repository has been picked up by MSYS2 and the Linux distributions which
provide cross-compilers themselves.
But this is all just my 2 cents.
Ruben
------------------------------------------------------------------------------
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
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
