# Cross-Compilation Cross-compilation is the process of building binaries for a different platform or architecture than the one running the compiler. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Cross-Compiling NixOS images DevFeed: [Cross-Compiling NixOS images]() Original publisher: [Read original article]() Author: Jacek Galowicz Published: 2025-12-20T00:00:00Z Content type: tutorial Language: en Sources: [Nixcademy Blog]() Topics: [Nix](), [Cross-Compilation](), [gnu linux](), [systemd]() Tags: [article](), [compilation](), [cross-compilation](), [how-to](), [learn](), [linux](), [systemd]() ### AI overview Part four of a series explaining how to cross-compile NixOS appliance images for other platforms while retaining Nix's declarative and composable configuration model. ### Source excerpt Part 4 of our NixOS appliance image series - Learn how to cross-compile NixOS images without losing declarativity and composability ## Cangjie -- a programming language from Huawei DevFeed: [Cangjie -- a programming language from Huawei]() Original publisher: [Read original article]() Author: Jasper Morgan Published: 2025-08-19T07:37:53Z Content type: opinion Language: en Sources: [Snapp Mobile - Medium]() Topics: [Programming language](), [huawei](), [Programming](), [Code](), [Embedded Systems](), [Cross-Compilation](), [Mobile](), [cloud-computing](), [Package Management](), [debug](), [Testing](), [ide]() Tags: [architectures](), [bytecode](), [cangjie](), [china](), [cloud](), [cross-compilation](), [debugging](), [developers](), [development](), [embedded-systems](), [huawei](), [huawei-developers](), [language](), [mobile](), [package-management](), [programming](), [programming-language](), [programming-languages](), [tools]() ### AI overview This article examines Cangjie, an open-sourced programming language from Huawei. It describes Cangjie as a C-like language with features associated with Swift and Kotlin, support for embedded systems, mobile development, and cloud architectures, interoperability with C and Python, JVM bytecode compilation, cross-compilation, and integrated developer tools. The article suggests Huawei created it to gain more control over its language roadmap and consolidate development skills across products. ### Source excerpt Cangjie -- a programming language from Huawei Huawei have been busy. Last month they open-sourced a programming language that is looking pretty interesting. Whilst you might not be writing in Cangjie next week, it's good to see what one of the world's largest technology companies is doing such that they have created a new programming language. TL;DR Cangjie is a C-like programming language that feels more like Swift/Kotlin than Java/C# or JavaScript/Typescript. The idea is for Cangjie to become the common programming language to be used throughout Huawei. Cangjie can be used for embedded systems, mobile development, server-side cloud architectures. It supports a variety of programming paradigms (function, OO, procedural), compilation and integration options. Cangjie can call C libraries (and be called from C), use Python libraries and even compile to JVM bytecode. Cangjie supports language extension to create lightweight DSLs. Primarily Cangjie programs are compiled into machine code -- this include cross compilation which mean they can run natively on different computer architectures. Cangjie comes with a set of in-built tools for developers such as package management, debugging, testing and IDE integration. Cangjie is openly available since this month and is in version 0.53.13. Why create a new language? Simply put, Cangjie gives Huawei a level of control and an economy of scale that they cannot get from other languages. Most mainstream languages are driven predominantly by teams in USA and Europe. It is hard to influence the road map for these languages -- especially for those tightly controlled by corporations (e.g. Java/Kotlin/Swift). Furthermore, consolidating programming skills could be a big efficiency gain for Huawei -- engineers working on products ranging from routers to petabyte storage to cloud computing and mobile devices can coalesce around one language and toolset. Show me some code I won't go into any detail here so this is just to satisfy your curiosit ## Using GoReleaser and GitHub Actions to release Rust and Zig projects DevFeed: [Using GoReleaser and GitHub Actions to release Rust and Zig projects]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2025-01-02T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Rust](), [Zig](), [GitHub Actions](), [Cross-Compilation](), [releases](), [configuration](), [Docker Image]() Tags: [changelog](), [cross-compilation](), [docker](), [github-actions](), [release](), [rust](), [zig]() ### AI overview A tutorial on using GoReleaser v2.5 with GitHub Actions to build, package, sign, and publish Rust and Zig projects across multiple platforms. It covers configuration, cross-compilation, changelog generation, Docker images, and release automation. ### Source excerpt GoReleaser v2.5 is out with Rust and Zig support - let's explore how we can use it! ## Nix Weekly Recap: 2024-02-18 DevFeed: [Nix Weekly Recap: 2024-02-18]() Original publisher: [Read original article]() Published: 2024-02-18T00:00:00Z Content type: article Language: en Sources: [nixpkgs.news]() Topics: [Nix](), [Cross-Compilation](), [Development](), [Security](), [Kernel](), [Virtual reality]() Tags: [community](), [cross-compilation](), [pull-requests](), [recap](), [repository](), [security](), [updates](), [weekly]() ### AI overview A weekly recap of announcements and development activity in the Nix community and Nixpkgs repository, including cross-compilation tooling, visual learning tools, merge automation, pull-request updates, and security patches. ### Source excerpt Weekly recap of the announcements and activity in the Nix community and on the NixPkgs package repository. ## Separation of Concerns in Cross-Compilation DevFeed: [Separation of Concerns in Cross-Compilation]() Original publisher: [Read original article]() Author: Jacek Galowicz Published: 2024-01-30T00:00:00Z Content type: tutorial Language: en Sources: [Nixcademy Blog]() Topics: [Cross-Compilation](), [Nix](), [C++](), [Dependency management](), [Compiler](), [Dockerfile](), [static linking]() Tags: [c-plus-plus](), [compilation](), [compiler](), [cross-compilation](), [dependency-management](), [development](), [docker](), [static-linking]() ### AI overview This guide explains how Nix applies separation of concerns to cross-compilation in complex C++ projects. It discusses compiler selection, dependency management, external libraries, distribution, Docker-based workflows, and static linking. ### Source excerpt Master cross-compilation in complex C++ projects with Nix. Simplify dependency management, boost development speed, and reduce costs with this guide! ## C++ with Nix in 2023, Part 2: Package Generation and Cross-Compilation DevFeed: [C++ with Nix in 2023, Part 2: Package Generation and Cross-Compilation]() Original publisher: [Read original article]() Author: Jacek Galowicz Published: 2023-11-16T00:00:00Z Content type: tutorial Language: en Sources: [Nixcademy Blog]() Topics: [Nix](), [C++](), [Cross-Compilation](), [Development](), [Code]() Tags: [build-system](), [c-plus-plus](), [cross-compilation](), [github](), [platforms](), [toolchain]() ### AI overview A tutorial on packaging C++ applications with Nix, using Nix package definitions and flakes to create reproducible builds, generate developer shells, run applications, swap compilers, and cross-compile for different platforms. ### Source excerpt Learn to package and cross-compile C++ apps with Nix in 2023. Use nix flakes, swap compilers, and cross-compile for various platforms effortlessly. ## How Go Compares with Other Languages for Cloud Backend Development DevFeed: [How Go Compares with Other Languages for Cloud Backend Development]() Original publisher: [Read original article]() Author: Marcus Kohlberg Published: 2023-02-27T00:00:00Z Content type: comparison Language: en Sources: [Encore Updates]() Topics: [Go Language](), [backend-development](), [Cloud](), [Programming language](), [Concurrency](), [distributed-systems](), [Cross-Compilation](), [Security]() Tags: [backend-development](), [cloud](), [compiled-language](), [concurrency](), [cross-compilation](), [distributed-systems](), [go](), [languages](), [scalability](), [security]() ### AI overview This article compares Go with other programming languages for building cloud backends. It attributes Go's suitability to compiled execution, memory management, concurrency through goroutines and channels, cross-compilation, and security-related features, while noting that cloud adoption has increased the importance of scalability, reliability, and cost control. ### Source excerpt A look at how Go compares to other languages when building cloud backends ## How a Kotlin Multiplatform library is published? DevFeed: [How a Kotlin Multiplatform library is published?]() Original publisher: [Read original article]() Author: Ekaterina Petrova Published: 2021-03-25T12:40:27Z Content type: tutorial Language: en Sources: [Kotlin]() Topics: [Kotlin Multiplatform](), [multiplatform](), [Library](), [Gradle](), [Maven](), [Cross-Compilation](), [iOS](), [macOS]() Tags: [coding](), [community](), [compilation](), [cross-compilation](), [development](), [engineering](), [gradle](), [inclusive](), [ios](), [kotlin](), [kotlin-multiplatform](), [libraries](), [library](), [macos](), [multiplatform](), [native](), [software]() ### AI overview This tutorial explains how Kotlin Multiplatform libraries are published. It describes the multiple artifacts, common and platform-specific source sets, Maven project coordinates, and platform constraints such as Kotlin/Native cross-compilation for iOS and macOS. ### Source excerpt In the first part of the series, we've created our first multiplatform library and published it to the local Maven. Before going public, let's discover published artifacts to get an understanding of the multiplatform publishing format. TL;DR: The Kotlin Gradle plugin creates and configures your library publications automatically, so you don't need to know the details of the publication scheme to successfully deliver your library. But if you are curious, let's discuss it a little! Discovering your library structure If you have published regular platform (for example, android) libraries before, you may notice that the publishing format of a multiplatform library differs quite a lot. There are multiple artifacts for one version of your library, their content format is different (.jar vs .klib), and the number of source sets doesn't match the number of result artifacts. This is because ordinary publishing is not enough for a multiplatform library. Multiplatform libraries have more complex structures compared to normal ones, so the publication is less trivial as well. Here are key differences to keep in mind: Multiplatform libraries consist of multiple parts: common parts with expects declarations and platform-specific parts with actual implementations. Platform-specific code may still be shared across similar platforms (e.g. in a source set shared between the iOS device and simulator, or shared code for all desktop platforms). There should be the ability to publish all those parts from a multiple host because of Kotlin/Native cross-compilation limitations. For example, the artifacts for iOS or macOS can be built only on Mac-OS. Considering all that complexity, adding the ordinary multiplatform dependency requires just a single line of code in your the build.gradle file: dependencies { implementation("io.github.katerinapetrova:mpp-sample-lib:1.0.0") } So how does this magic work? Maven doesn't operate with targets, source sets, and compilations. It operates only with pro ## February 2021 round-up DevFeed: [February 2021 round-up]() Original publisher: [Read original article]() Author: Samuel Dionne-Riel Published: 2021-03-02T00:00:00Z Content type: news Language: en Sources: [Mobile NixOS news]() Topics: [Nix](), [Mobile](), [Cross-Compilation](), [pull-requests](), [Android](), [boot]() Tags: [android](), [boot](), [cross-compilation](), [flashing](), [pull-requests](), [update](), [zip]() ### AI overview This fifteenth Mobile NixOS project update reports 18 merged pull requests and describes more hermetic evaluation without NIX_PATH, completed stage-0 boot features, restored armv7 support, and Android flashable ZIP support. ### Source excerpt This update is the fifteenth in a series of regular updates on the state of the project. Only changes that have been accepted and merged in Mobile NixOS are chronicled here. There's always more work currently in-progress. Notable changes During the month 18 pull requests were merged. Compared to the last month, they're more subtle changes. More hermetic evaluation This started off the work from @eamsden, where uses of were removed almost everywhere in #238. With the changes, the value is now used only at one location, at the start of the evaluation, in a way that can be overridden easily if needed. This means that evaluation now works fine without a NIX_PATH. This is useful to allow users of Nix flakes to use the project. Similar changes were made in #310 to rely on a single value for release.nix and example configuration evaluations. Finalize stage-0 When #262 was merged in December, it was done so with two main features missing. Time was taken to finish the boot features for stage-0 in #300. When a device supports stage-0 boot, a new toggle is shown in the generations list allowing the user to skip rebooting into the generation's kernel. When booting a generation, the device tree built from the same kernel source tree is now used. The pull request itself contains technical details. This was less trivial than expected. armv7 works again Using armv7 with Nixpkgs or NixOS is not always easy. There is no binary cache, and cross-compilation is as YMMV as it is for AArch64. This is the reason why armv7 Mobile NixOS devices haven't seen much work done and things slowly started not working. With #306 time was taken to ensure contributors with armv7 devices wouldn't be left with hard to debug issues from Mobile NixOS itself. With this work finally taken care of, there is a recent known good starting point to use for armv7 devices. A few recent WIP device ports were made on top of these changes. Stay tuned as they may become supported devices a ## Cross-compiling with musl Toolchains DevFeed: [Cross-compiling with musl Toolchains]() Original publisher: [Read original article]() Published: 2020-06-22T12:37:59Z Content type: tutorial Language: en Sources: [Ariya Hidayat]() Topics: [Cross-Compilation](), [toolchains](), [Linux](), [Zig](), [C](), [qemu](), [ci](), [make]() Tags: [c](), [compiler](), [continuous-integration](), [cross-compilation](), [docker](), [linux](), [make](), [mips](), [qemu](), [toolchains](), [windows](), [x86]() ### AI overview A tutorial on using static musl-based toolchains to cross-compile command-line programs for multiple targets, including MIPS and Windows, from a Linux x86-64 host. It also covers testing non-native binaries with QEMU and migrating FastLZ continuous integration to musl.cc. ### Source excerpt When working on command-line utilities which can be useful for various platforms, from Windows on x86 to Linux on MIPS, the existence of a cross-compilation is highly attractive. A number of different binaries can be constructed conveniently from a single, typically powerful host system. ## March 2020 round-up DevFeed: [March 2020 round-up]() Original publisher: [Read original article]() Author: Samuel Dionne-Riel Published: 2020-04-07T00:00:00Z Content type: news Language: en Sources: [Mobile NixOS news]() Topics: [Mobile](), [Nix](), [Hardware](), [boot](), [Cross-Compilation](), [Kernel](), [Wi-Fi]() Tags: [boot](), [cross-compilation](), [hardware](), [kernel](), [mobile](), [news](), [update](), [wi-fi]() ### AI overview This March 2020 Mobile NixOS project update reports 17 merged pull requests, including PinePhone support through a new U-Boot system type. It also covers universal stage-2 images, Hydra-based continuous builds, pre-built rootfs images, and progress toward cross-compilation. ### Source excerpt This update is the fifth in a series of regular updates on the state of the project. Only changes that have been accepted and merged in Mobile NixOS are chronicled here. There's always more work currently in-progress. Notable changes 17 PRs were merged during the month. (The link says 18, but one of them was, to me, late in February, read the previous news item). Let's look at some of these. Pine64 Pinephone "Braveheart" This was teased about on the author's twitter account. The inexpensive Pinephone is the latest new device added to Mobile NixOS. This brings a bit more than only a new device. This is the fourth system type added to Mobile NixOS. The added system type (U-Boot) in theory will give us the ability to support any U-Boot-based system in a common way. In practice the still unmerged and WIP #94 shows how this is true by using U-Boot with another Pine64 device, the Pinebook Pro. A nice thing that was verified again with this new device port is that the stage-2 image (the rootfs, the system.img) is indeed universal. It is using the same AArch64 build of the system image as Android-based devices, and Depthcharge-based devices. Our build for the Pinephone relies on the downstream kernel from the Pine64 community, with only one added patch. The same is done for the U-Boot build. The added patches are user-experience-focused patches that are using the RGB LED of the phone to show the boot status. Other than that, the hardware support is not complete, but it is supported at the same level as other devices, plus Wi-Fi working. See PR #96 for all the details. Hydra builds This is not entirely an in-repository change. There's #97 and #133 that are relevant to this. The mobile-nixos:unstable jobset on Hydra is the other part of the puzzle. What this gives us is automatic continuous builds of Mobile NixOS against the nixos-unstable NixOS channel. From this, we can track changes that break the Mobile NixOS builds, and track internal breakage to some parts of Mobile Nix ## Cross Compiling with Docker on WSL 2 DevFeed: [Cross Compiling with Docker on WSL 2]() Original publisher: [Read original article]() Published: 2019-06-30T21:24:51Z Content type: tutorial Language: en Sources: [Ariya Hidayat]() Topics: [Windows Subsystem for Linux](), [Cross-Compilation](), [Docker](), [qemu](), [C](), [Ubuntu](), [Windows](), [WebAssembly]() Tags: [arm](), [c](), [containers](), [cross-compilation](), [docker](), [qemu](), [ubuntu](), [webassembly](), [windows](), [wsl]() ### AI overview This tutorial explains how to use Docker on WSL 2 to cross-compile a simple C program for ARMv7. It uses Dockcross for Docker-based cross-compilation, QEMU to run the resulting ARM binary, and briefly describes targets including MIPS, PowerPC, Windows, and WebAssembly. ### Source excerpt Now that WSL 2 packs a true Linux kernel and supports Linux containers (via Docker), it can be a perfect setup to perform application cross compilations. ## Engineering Manager Framework: How to Evaluate Mobile Multiplatform Solutions - Justin Mancinelli DevFeed: [Engineering Manager Framework: How to Evaluate Mobile Multiplatform Solutions - Justin Mancinelli]() Original publisher: [Read original article]() Published: 2019-04-15T21:32:04Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Mobile](), [multiplatform](), [Framework](), [Kotlin Multiplatform](), [Cross-Compilation](), [Ionic](), [React Native](), [Flutter](), [Xamarin]() Tags: [blog-post](), [code-sharing](), [cross-compilation](), [framework](), [kotlin-multiplatform](), [mobile](), [multiplatform]() ### AI overview This article presents a framework for evaluating mobile multiplatform solutions by examining the input language, build process, runtime, and application output. It distinguishes native, hybrid, and web applications and applies the framework to Ionic, React Native, Xamarin, and Flutter. ### Source excerpt Touchlab's Director of Project Strategy Justin Mancinelli discusses a framework for how to evaluate mobile multiplatform solutions. ## State of Gradle Java 9 Support DevFeed: [State of Gradle Java 9 Support]() Original publisher: [Read original article]() Author: Eric Wendelin Published: 2017-10-17T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Java](), [Cross-Compilation](), [modules](), [Architecture & Design]() Tags: [cross-compilation](), [gradle](), [java](), [java-9](), [module](), [security](), [software-architecture]() ### AI overview This article explains Gradle's Java 9 support as of Gradle 4.2.1. It covers running and building applications with major JDK 9 distributions, cross-compilation from JDK 9 to JDK 8, limitations around Multi-Release JARs, and using Java 9 modules with Gradle. ### Source excerpt This post provides an overview of Gradle's Java 9 support, touching on runtime, cross-compilation, MRJARs, and Jigsaw modules support. We've fielded lots of questions since Java 9 was released last month, and decided it best to answer here. What Gradle supports as of version 4.2.1 As of Gradle 4.2.1, building and running Java applications using major distributions of JDK 9 such as Oracle JDK9, OpenJDK9 and Azul JDK9 is fully supported. Further, cross-compilation (built by JDK9 but runs on JDK8) is supported. Some builds will break when upgrading to Java 9, regardless of build tool used. The Java team have made good and necessary changes to the JDK to facilitate better software architecture and security, but this has meant removing access to some APIs. Even if your project is ready, some tools and Gradle plugins have not yet been updated to work with Java 9. There is no convenience methods for consuming and assembling Multi-Release JARs, but you can take a look at this MRJAR-gradle example if you desire to use them. Java Modules aka Jigsaw Support If you're not yet familiar with the Java 9 Platform Module System, also known as Project Jigsaw, you should read Project Jigsaw: Module System Quick-Start Guide. The motivation and terminology are well explained in The State of the Module System. A module is defined as "a named, self-describing collection of code and data" whereby packages are treated as code boundaries, and are explicitly exported and required. Non-exported packages are not visible to module consumers, and further 2 modules cannot export the same packages, nor can they have the same internal packages. This means that packages cannot be "split" or duplicated between multiple modules, or compilation will fail. Here is a guide that shows how to use Java modules with Gradle today. It walks you through the steps necessary to tell Gradle to use the modulepath and not classpath when compiling Java sources and patch modules for testing purposes. A bottom-up approa ## Go: Targeting a different architecture #golang DevFeed: [Go: Targeting a different architecture #golang]() Original publisher: [Read original article]() Author: Graham King Published: 2012-06-14T00:08:58Z Content type: tutorial Language: en Sources: [Graham King]() Topics: [Cross-Compilation](), [Go Language](), [Compiler]() Tags: [compilation](), [compiler](), [cross-compilation](), [go](), [software]() ### AI overview A short guide to building Go programs for a different architecture, such as building for amd64 from an i386 machine. It covers obtaining or building the compiler for the target architecture and setting the architecture before compiling the program. ### Source excerpt Problem: You're on a i386 machine, and you need to build for amd64, or vice-versa. Solution: Get the for the other architecture. Get both, one of which you'll already have: Build the Go compiler for the other architecture: Set the architecture before building your program: The first two steps you only need to do once. Thank you zephyrtronium in freenode#go-nuts for the help. For other architectures, see Dave Cheney's An introduction to cross compilation with Go