mxe
BinaryBuilder.jl
Our great sponsors
mxe | BinaryBuilder.jl | |
---|---|---|
9 | 5 | |
1,157 | 378 | |
1.3% | 1.3% | |
9.5 | 6.7 | |
4 days ago | 13 days ago | |
Makefile | Julia | |
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
- 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.
BinaryBuilder.jl
-
Is Julia suitable today as a scripting language?
There are some efforts and the startup times are getting better with every release and there's BinaryBuilder.jl.
-
Because cross-compiling binaries for Windows is easier than building natively
There is the Julia package https://github.com/JuliaPackaging/BinaryBuilder.jl which creates an environment that fakes being another, but with the correct compilers and SDKs . It's used to build all the binary dependencies
-
Discussion Thread
https://binarybuilder.org/. You can do it manually obviously, but this is easier.
-
PyTorch: Where we are headed and why it looks a lot like Julia (but not exactly)
> The main pain point is probably the lack of standard, multi-environment packaging solutions for natively compiled code.
Are you talking about something like BinaryBuilder.jl[1], which provides native binaries as julia-callable wrappers?
--
[1] https://binarybuilder.org
-
What to do about GPU packages on PyPI?
Julia did that for binary dependencies for a few years, with adapters for several linux platforms, homebrew, and for cross-compiled RPMs for Windows. It worked, to a degree -- less well on Windows -- but the combinatorial complexity led to many hiccups and significant maintenance effort. Each Julia package had to account for the peculiarities of each dependency across a range of dependency versions and packaging practices (linkage policies, bundling policies, naming variations, distro versions) -- and this is easier in Julia than in (C)Python because shared libraries are accessed via locally-JIT'd FFI, so there is no need to eg compile extensions for 4 different CPython ABIs (Julia also has syntactic macros which can be helpful here).
To provide a better experience for both package authors and users, as well as reducing the maintenance burden, the community has developed and migrated to a unified system called BinaryBuilder (https://binarybuilder.org) over the past 2-3 years. BinaryBuilder allows targeting all supported platforms with a single build script and also "audits" build products for common compatibility and linkage snafus (similar to some of the conda-build tooling and auditwheel). There was a nice talk at AlpineConf recently (https://alpinelinux.org/conf/) covering some of this history and detailing BinaryBuilder, although I'm not sure how to link into the video.
All that to say: it can work to an extent, but it has been tried various times before. The fact that conda and manylinux don't use system packages was not borne out of inexperience, either. The idea of "make binaries a distro packager's problem" sounds like a simplifying step, but that doesn't necessarily work out.
What are some alternatives?
llvm-mingw - An LLVM/Clang/LLD based mingw-w64 toolchain
functorch - functorch is JAX-like composable function transforms for PyTorch.
seer - Seer - a gui frontend to gdb
Yggdrasil - Collection of builder repositories for BinaryBuilder.jl
quasi-msys2 - Cross-compile C/C++ from Linux to Windows using MSYS2 packages
HTTP.jl - HTTP for Julia
displaylink-rpm - RPM sources for the DisplayLink USB display adapters
dh-virtualenv - Python virtualenvs in Debian packages
manylinux - Python wheels that work on any linux (almost)
RDKit - The official sources for the RDKit library
glibc_version_header - Build portable Linux binaries without using an ancient distro
StarWarsArrays.jl - Arrays indexed as the order of Star Wars movies