mxe-STATIC
mxe
| mxe-STATIC | mxe | |
|---|---|---|
| 1 | 9 | |
| 4 | 1,167 | |
| - | 1.2% | |
| 1.8 | 9.5 | |
| almost 2 years ago | 4 days ago | |
| C | Makefile | |
| GNU General Public License v3.0 or later | 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.
mxe-STATIC
-
The move to shared libraries in ARM32 MXE
I know this may be random, but it may be good for some application porters. For some context, I have a modified version of MXE on my ARM32 Windows organization (https://github.com/armdevvel/mxe), but every library builds as static, setting aside a few. This doesn't sound like a big deal, but it really causes a few issues:
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.
What are some alternatives?
woa-raphael - A guide on how to install Windows on Redmi K20 Pro / Mi 9T Pro
llvm-mingw - An LLVM/Clang/LLD based mingw-w64 toolchain
seer - Seer - a gui frontend to gdb
quasi-msys2 - Cross-compile C/C++ from Linux to Windows using MSYS2 packages
displaylink-rpm - RPM sources for the DisplayLink USB display adapters
manylinux - Python wheels that work on any linux (almost)
glibc_version_header - Build portable Linux binaries without using an ancient distro
ded - Dramatic EDitor
BinaryBuilder.jl - Binary Dependency Builder for Julia
WSL - Issues found on WSL
AppImageKit - Package desktop applications as AppImages that run on common Linux-based operating systems, such as RHEL, CentOS, openSUSE, SLED, Ubuntu, Fedora, debian and derivatives. Join #AppImage on irc.libera.chat
xwin - A utility for downloading and packaging the Microsoft CRT headers and libraries, and Windows SDK headers and libraries needed for compiling and linking programs targeting Windows.