llvm-mingw
WSL
llvm-mingw | WSL | |
---|---|---|
15 | 406 | |
1,638 | 16,652 | |
- | 0.6% | |
8.8 | 8.6 | |
3 days ago | 6 days ago | |
C | PowerShell | |
GNU General Public License v3.0 or later | MIT License |
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.
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.
WSL
-
GoboLinux
It absolutely 100% can be true.
As an example: Windows Services for Linux 2 used a special init daemon to interact with the host OS.
That meant no systemd. That meant that the `systemctl` program wasn't there.
This baffled legions, armies, of wannabe sysadmins.
https://stackoverflow.com/questions/55579342/why-systemd-is-...
https://superuser.com/questions/1785697/systemd-in-wsl-on-wi...
https://github.com/microsoft/WSL/issues/9477
https://askubuntu.com/questions/1132230/unable-to-run-any-sy...
People on the whole have no idea how this stuff works, and they just copy magic incantations from StackOverflow to get stuff to happen. If that doesn't work, then this OS is broken. The end.
For these guys, WSL was broken.
Result:
MS hired Lennart Poettering.
https://www.theregister.com/2022/07/07/lennart_poettering_re...
He "fixed" it. Systemd now works in WSL2. All those guides for noobs now work. Everyone is happy.
In a world where tools like Flatpak and Snap are proliferating and it's driving deep divisions between Linux distros, if you think the average person struggling with Linux is going to use `ldd` to work out where the dependencies for something live, I'm afraid you are a deep guru who lives on a different plane of existence.
We now have widely-used packaging systems which simply embed an apps entire dependency tree into a package to avoid people having to work out the difference between `apt` and `rpm`. Thousands of terabytes of disk are being burned to make this stuff go away.
Yes, this is too hard. Way too hard.
-
Why Linux utilities tend to run poorly on Windows
Better source: https://github.com/Microsoft/WSL/issues/873#issuecomment-425...
- Weird graphical glitch/problem in Ubuntu WSLg (OpenGL)
-
RamRamRamEveryoneSleepingOnDocker
One of the bugs where on the Docker side. As I have said, there have been several since release with a lot of impact period overlap. The latest and greatest is not resolved.
-
Laravel dev in Windows - Laragon vs Docker?
It's the issue of abysmal I/O performance in communication between the mounted WSL2 virtual hard disk and Windows mounts inside the WSL2 distro.
- WSL freeze seems fixed in 2.0.12
-
What's the right way to open files in the system's default program from Ubuntu 22.04 in WSL 2 please?
I found this github page and I was able to reproduce this from the answer
-
Ask HN: Best Docker open source alternative?
* Docker engine and not Docker Desktop in a VM. WSL2 works well after some configuration: https://github.com/microsoft/WSL/issues/6655#issuecomment-11...
-
Broadcom to Cut Almost 1,300 VMware Jobs in California After Takeover
Seems to more of a Defender issue than a WSL one, see https://github.com/microsoft/WSL/issues/8995
After adding exclusions for the fsnotifier-wsl process and and both variants of the WSL distro path my disk performance was improved.
Adding the idea64.exe process also helped since I was trying to run IntelliJ against projects inside WSL.
- Bricked WSL 2 after 2.0.9 / Windows 10
What are some alternatives?
mingw-w64 - (Unofficial) Mirror of mingw-w64-code
wslg - Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
w64devkit - Portable C and C++ Development Kit for x64 (and x86) Windows
genie - A quick way into a systemd "bottle" for WSL
msys2
Scoop - A command-line installer for Windows.
cmake-init - The missing CMake project initializer
Single-GPU-Passthrough
MSYS2-packages - Package scripts for MSYS2.
setup-msys2 - GitHub Action to setup MSYS2
mxe - MXE (M cross environment)
mkcert - A simple zero-config tool to make locally trusted development certificates with any names you'd like.