mxe | WSL | |
---|---|---|
9 | 406 | |
1,164 | 16,676 | |
0.9% | 0.7% | |
9.5 | 8.6 | |
4 days ago | 3 days ago | |
Makefile | 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.
mxe
- MXE (M Cross Environment)
-
Using pybind11 with minGW to cross compile pyhton module for Windows
Cross compiler 64bit minGW along with MXE environment
- Getting “QT with MinGW support”?
-
Because cross-compiling binaries for Windows is easier than building natively
I used to use MXE [1] to compile fully static Windows binaries on Linux VMs hosted with Travis. It needed to crane in everything though, so it was a source of bottlenecks from time to time. I was also uncertain about the provenance of a lot of the dependencies in that toolchain. So when Travis died I took the opportunity to move Windows builds back to gnu with msys2, all over GH Actions. These are actually comparatively snappy and I’m reasonably satisfied with it.
[1] https://mxe.cc/
-
Linux-to-Windows cross-compilation using MSYS2 packages
MXE readily supports GCC 12 as a plugin (just a configuration line): https://github.com/mxe/mxe/tree/master/plugins/gcc12
-
Seer - a new gui frontend to gdb/mi (Updated v1.3)
Also, if you don't have any other significant dependencies, getting the development tools on Windows is not that hard with the Qt installer. Alternatively, there is MXE.
-
Writing code in Linux, but creating a program in windows.
MXE (https://mxe.cc/) is a great cross compiler environment (on linux) that uses mingw.
-
Cross-compilation on a mac
You can install Docker to build on any Linux distro, and if one of those is Ubuntu then you can use https://github.com/mxe/mxe to further build for Windows. Or VirtualBox + Ubuntu + MXE.
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?
llvm-mingw - An LLVM/Clang/LLD based mingw-w64 toolchain
wslg - Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
seer - Seer - a gui frontend to gdb
genie - A quick way into a systemd "bottle" for WSL
quasi-msys2 - Cross-compile C/C++ from Linux to Windows using MSYS2 packages
Scoop - A command-line installer for Windows.
displaylink-rpm - RPM sources for the DisplayLink USB display adapters
Single-GPU-Passthrough
manylinux - Python wheels that work on any linux (almost)
setup-msys2 - GitHub Action to setup MSYS2
glibc_version_header - Build portable Linux binaries without using an ancient distro
mkcert - A simple zero-config tool to make locally trusted development certificates with any names you'd like.