22 нояб. 2013 г., в 17:05, Ruben Van Boxem <[email protected]>
написал(а):
> Hi everyone,
>
> I'd like to thank the MSYS2 devs for their excellent work on getting this
> quick and dirty POSIX shell/development environment working. Although I never
> use it anymore, it had its uses to me at one point and can appreciate the
> availability of an up to date version.
>
> Lately, though, I've bee surprised by the number of things people want to
> stuff into MSYS2. I alwas ahd the impression MSYS was a minimal system which
> contains a bunch of POSIX shell tools to accomodate configure scripts and
> UNIX-y makefiles.
>
> There have been requests for things like X, CMake and other things that in my
> eyes make absolutely no sense to be even remotely related to MSYS. If you
> need a full POSIX OS-emulating environment, use Cygwin. If you need a shell,
> use MSYS. W.r.t. CMake: there is no use for there to be an MSYS port of this
> for two reasons: CMake works fine as a pure Win32 app, and it can generate
> MSYS makefiles.
>
> I have forgotten other examples, but please, don't just build stuff for MSYS
> because you can. That's just a waste of time and ridiculous.
>
> Also: I implore you to explore (ha, two -plores in one sentence) the use of
> the existing AUR PKGBUILDs for MinGW-w64 package creation. It makes
> absolutely no sense to spread efforts if you want a complete package
> management system. They are perfectly usable, all you need to do is change
> your toolchains' paths to more sensible ([/usr]/[x86_64|i686]-w64-mingw32
> install prefix) defaults to match the Linux setup. This allows you to use the
> existing PKGBUILDs *unmodified*, which is a huge advantage!
>
> Anyways, just a Friday afternoon rant I hope will be taken into serious
> consideration.
>
> Cheers,
>
> Ruben
Thanks Ruben for your point of view! I hear your voice)
I don’t want to add more packages for MSYS2 except maybe some perl modules.
Instead adding msys2 packages we can work on adding packages for MINGW repos
that I already create and place mingw toolchains there.
About using AUR PKGBUILD’s:
- mingw packages builing in cycle for architectures and to build it under
msys2 with native toolchain we need to substitute PATH variable on every
iteration. Thats why it some difficult. This PKGBUILD’s can be successfully
using with cross mingw toolchains only.
Regards,
Alexey.
------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
