MSYS2-packages
llvm-mingw
MSYS2-packages | llvm-mingw | |
---|---|---|
10 | 15 | |
1,250 | 1,638 | |
0.7% | - | |
9.8 | 8.8 | |
5 days ago | 4 days ago | |
Shell | C | |
BSD 3-clause "New" or "Revised" License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
MSYS2-packages
- How to start msys2-shell with fish-shell
-
MSYS2 Installation
Google says (1, 2, 3) that this issue is caused by Avast/AVG antivirus moving some executable files (bash.exe in your case, seemingly) into its quarantine folder.
-
Colorscheme problems when using MinTTY as the terminal for nvim.
It's a known issue: https://github.com/msys2/MSYS2-packages/issues/3150
-
Erdtree v1.4.1 - the love child of `tree` and `du`, now with support for a configuration file to override defaults and more
Could you let me know of this is perhaps relevant to you? I will investigate sometime this week! Thanks for bringing this to my attention.
-
Windows Subsystem For Linux a.k.a. WSL 1.0.0 released
I am still on WSL1 due to the filesystem performance with WSL2. I recently tried to move more of my workflow towards MSYS2 but various things keep breaking for me without obvious reasons.
Latest issue I encountered was that GNU parallel simple does not work. [1]
[1]: https://github.com/msys2/MSYS2-packages/issues/3289
-
Getting GTK3 in WINE?
I've already tested the rest of the tools needed for the build process (just Python 3.10 and PyInstaller) and they seem to work fine. My issue is that both MSYS2 and Cygwin do not work in WINE (this is pretty well documented: MSYS2, Cygwin), so I don't know of any other means of getting the Windows versions of GTK3 libraries in my WINE prefix so that PyInstaller can pack it all up for me.
- Bug on fresh installation · Issue #2295 · msys2/MSYS2-packages
- zsh completion issue · Issue #38 · msys2/MSYS2-packages
-
copy_file with overwirte_existing throws exception when the file exists
It's old bug with gcc standard library implementation which has not been fixed, I guess most likely nobody made a bug report. I tested it myself and indeed it doesn't work properly and we are not alone: https://github.com/msys2/MSYS2-packages/issues/1937.
-
The Atrocities of COM win32 headers
My last experience with MinGW-w64 was when I was trying to compile my C++ simulation code in Windows and finding out that AVX instructions were not working because the compiler had misalignment-related bugs. (The issue is still open in https://github.com/msys2/MSYS2-packages/issues/1209)
MinGW/MSYS certainly had appeal to former Linux devs who didn't want to touch the horrors of MSVC, but Zig (with its included Clang compiler/runtime) might end up being a better solution for people trying to compile C/C++ code on Windows in a stable manner.
llvm-mingw
- Crystal 1.11.0 Is Released
-
Ask HN: Who is using the D language and likes/doesn't like it? Why?
> Doing Python with a C plugin, or just compiling a command line C/C++ isn't really systems programming.
I care about a minimal set of tools in order to compile C/C++ programs. thats offered by:
https://github.com/mstorsjo/llvm-mingw/releases
and also MSYS2, and even the Zig C compiler. all less than 200 MB. meanwhile Visual Studio installing about 10 GB worth. If Microsoft can offer a similar experience then I am interested.
-
Clang compiler for Windows 10 gives this error
Pick a community-supported Clang-based Mingw-w64 distribution.
-
My 24 year old HP Jornada can do things your modern iPhone still can't do
> AFAIK there is no native GCC compiler for Windows
might want to check your facts before spouting nonsense. there is, and has been for many, many years. more than one in fact:
https://github.com/mstorsjo/llvm-mingw
https://packages.msys2.org/base/mingw-w64-gcc
-
Release candidate: Godot 4.0 RC 5 (Yes, the pace is picking up!)
MinGW is notoriously slow to link compared to MSVC, unless using llvm-mingw with the link=lld SCons option. If using MSVC, make sure to use 2022 or at least 2019 if possible – recent linkers tend to be faster than older versions.
-
Toolchain for cross-compiling DLL to windows/arm64
GCC doesn't support windows/arm64, but you should be able to do it with LLVM. I've never gotten it to work myself, but should be able to supply a cross toolchain: https://github.com/mstorsjo/llvm-mingw
-
Ask HN: Programming Without a Build System?
Visual Studio is a bloated mess, and has been for many years. Its at least 10 times larger than other options, such as MinGW-LLVM:
https://github.com/mstorsjo/llvm-mingw
-
Because cross-compiling binaries for Windows is easier than building natively
Sadly Qt ships MinGW 8.1 which is positively ancient (released in 2018). If you're starting a new project (which you likely are if you are installing an IDE aha) there's no reason not to go for more recent compilers - msys2 has GCC12 (https://packages.msys2.org/package/mingw-w64-x86_64-gcc) and Clang 14 (https://packages.msys2.org/package/mingw-w64-x86_64-clang) which just work better overall, have much more complete C++20 support, have less bugs, better compile times (especially clang with the various PCH options that appeared in the last few versions), better static analysis, etc.
Personally I use https://github.com/mstorsjo/llvm-mingw's releases directly which does not require MSYS but that's because I recompile all my libraries with specific options - if the MSYS libs as they are built are good for you there's no reason not to use them.
-
Some sanity for C and C++ development on Windows
you can grab it here: https://github.com/mstorsjo/llvm-mingw/releases/tag/20211002
-
The Atrocities of COM win32 headers
Clang (and lld) do support native TLS, and mingw-w64 does have the things that are needed. I think binutils also might have what's needed too, but AFAIK the thing that's missing is support for it in GCC.
Actually, (upstream) Clang defaults to native TLS instead of emulated TLS. In MSYS2, Clang is overridden to use emulated TLS by deafult to interoperate better with GCC built code and libstdc++ though.
The toolchain I maintain, https://github.com/mstorsjo/llvm-mingw, defaults to native TLS throughout.
What are some alternatives?
mingw-w64 - (Unofficial) Mirror of mingw-w64-code
glibc-abi-tool - A repository that collects glibc .abilist files for every version and a tool to combine them into one dataset.
w64devkit - Portable C and C++ Development Kit for x64 (and x86) Windows
media-autobuild_suite - This Windows Batchscript helps setup a Mingw-w64 compiler environment for building ffmpeg and other media tools under Windows.
msys2
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
cmake-init - The missing CMake project initializer
qmk_distro_msys - A Windows one-click installer for the QMK CLI
mxe - MXE (M cross environment)
rubyinstaller2 - MSYS2 based RubyInstaller for Windows