manylinux
osxcross
manylinux | osxcross | |
---|---|---|
13 | 23 | |
1,355 | 2,737 | |
1.8% | - | |
8.8 | 5.5 | |
4 days ago | about 1 month ago | |
Shell | C++ | |
MIT License | GNU General Public License v3.0 only |
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.
manylinux
-
Building a go program with an older glibc
I use manylinux containers as the OS for compilation. It tries to ensure as much cross-os / libc / etc.. as much as possible for precompiled libraries. https://github.com/pypa/manylinux
-
Alpine Linux in the Browser
Just to clarify for anyone who isn't aware, the "compiling issues", at least historically, have been that that Alpine uses musl, and PyPI's manylinux wheels are built against old glibc versions. So stuff like numpy that would trivially and quickly install from whl on glibc distros (like a bare-bones Ubuntu image) trigger compilations and the installation of build-only dependencies on Alpine.
That said, it looks like as of late-2021, at least some projects are offering musllinux wheels as well, per the discussion here: https://github.com/pypa/manylinux/issues/37 (not numpy, though: https://pypi.org/project/numpy/#files)
-
Because cross-compiling binaries for Windows is easier than building natively
It's very hard. Incompatible glibc ABIs make this nigh impossible, there's a reason Steam installs a vcredistributable.dll for pretty much every game on Windows.
Look no further than the hoops you need jump through to distribute a Linux binary on PyPI [1]. Despite tons of engineering effort, and tons of hoop jumping from packagers, getting a non-trivial binary to run across all distros is still considered functionally impossible.
[1]: https://github.com/pypa/manylinux
- manylinux_2_28 image is published
- manylinux_2_28 image is published (including docker environment)
-
CPython, C standards, and IEEE 754
As a user, if you build every python package from source, it's ok. But if you a maintainer of an OSS project and you need to publish binary packages for it, then you will hit the trouble. Binaries built on Ubuntu 20.04 can only support Ubuntu 20.04 and newer. So you'd better to choose an older Linux release to target broader users. Now most python packages choose CentOS 6 or 7. See https://github.com/pypa/manylinux/issues/1012 for more details. They need help!
-
Using Zig as Cross Platform C Toolchain
I recently learned that Clang supports this kind of cross-compiling out of the box. https://mcilloni.ovh/2021/02/09/cxx-cross-clang/
The main difference is that Clang does not ship with headers/libraries for different platforms, as Zig appears to do. You need to give Clang a "sysroot" -- a path that has the headers/libraries for the platform you want to compile for.
If you create a bunch of sysroots for various architectures, you can do some pretty "easy" cross-compiling with just a single compiler binary. Docker can be a nice way of packaging up these sysroots (especially combined with Docker images like manylinux: https://github.com/pypa/manylinux). Gone are the days when you had to build a separate GCC cross-compiler for each platform you want to target.
- “LLVM-Libc” C Standard Library
-
'Python: Please stop screwing over Linux distros'
Now you come and use manylinux to build. (https://github.com/pypa/manylinux) so you are based on the CentOS 7 toolchain (at best if you use manylinux2014) or Debian 9 toolchain (if you use manylinux_2_24).
-
Building Outer Wonders for Linux
I think the generally accepted way to do that would be a container image running a relatively old distribution. This is exactly what python packages do when they need to distribute binary packages on linux [0]. You are supposed to compile the package in a container (or VM) that runs CentOS 7 (or older if you want broader support), although now the baseline is moving gradually to Debian 9.
[0]: https://github.com/pypa/manylinux
osxcross
- Darling: Run macOS Software on Linux
-
How to cross Compile on Debian for: Mac / FreeBSD / OpenBSD / Android ... ?
If you actually have MacOS device and can install Xcode and so on then you can proceed here and read the instructions.
-
I find it's not possible to do serious C/C++ coding on latest macOS
Have you considered using a dockerized osxcross cross compiler toolchain in your CI? Granted it is a bit clunky to setup...
-
Apple just lost its lawsuit trying to ban iOS virtual machines
Technically it's possible, but possibly not legal:
https://github.com/tpoechtrager/osxcross
> Please ensure you have read and understood the Xcode license terms before continuing.
According to the EULA you may only use the SDK on Apple-branded computers. But you can use Linux to cross compile to Apple.
- Go port of SQLite without CGo
-
Cross compile for ppc macs (10.4)
is there a way to cross compile without vms? something similar to https://github.com/tpoechtrager/osxcross?
-
Am looking for an API guru to assess how to make a project multiplatform
If you figure out how to get SDL working, one possibility is to develop on Linux, then use mingw-w64 to cross compile from Linux to windows, then use osxcross to cross-compile from Windows to OSX.
- How To Fix Your Computer
-
Rust & Cross-compiling from Linux to Mac on GitHub Actions
Thank you osxcross for creating the path forward
-
A Completely Open-Source Implementation of Apple Code Signing and Notarization
This is actually a solved problem, using osxcross[0]. The experience is honestly very smooth, and we don't require any apple proprietary binaries. The only thing apple-proprietary is their SDK (containing the header files for compiling, and tbd files for linking), which can be downloaded from apple's website (at least if you have a developer account), or from various GitHub projects archiving them.
[0]: https://github.com/tpoechtrager/osxcross
What are some alternatives?
auditwheel - Auditing and relabeling cross-distribution Linux wheels.
mold - Mold: A Modern Linker 🦠
musl-cross-make - Simple makefile-based build for musl cross compiler
eShopOnContainers - Cross-platform .NET sample microservices and container based application that runs on Linux Windows and macOS. Powered by .NET 7, Docker Containers and Azure Kubernetes Services. Supports Visual Studio, VS for Mac and CLI based environments with Docker CLI, dotnet CLI, VS Code or any other code editor. Moved to https://github.com/dotnet/eShop.
glibc_version_header - Build portable Linux binaries without using an ancient distro
fltk-rs - Rust bindings for the FLTK GUI library.
mxe - MXE (M cross environment)
xcgo - Golang cross-platform builder docker image with CGo and other tooling
lhelper - A simple utility to helps compile and install C/C++ libraries on Windows and Linux
SDL - Simple Directmedia Layer
docker-go-mingw - Docker image for building Go binaries with MinGW toolchain