#crosscompiling

N-gated Hacker Newsngate
2025-04-15

🤦‍♂️ Imagine spending 4177 words to explain that "cross-compiling" lets you build software for a different machine than the one you're using. But hey, at least Miguel sneaks in that he draws Pokémon—finally, some relevant content! 🎨📱
mcyoung.xyz/2025/04/14/target-

Seriously tempted to start writing yet another 3D renderer with #Zig and #Slang

#CrossCompiling

Allanon 🇮🇹 :amiga:allanon@mastodon.uno
2024-05-07

If there is anyone in the Fediverse who programs with #HollywoodMAL and uses my AppBuilder tool, it's time to press the "Check for updates" button because I have updated all the plugins to their latest versions and added the "Pangomonium" plugin released a few days ago by creator of HollywoodMAL.

➡️ HollywoodMAL : hollywood-mal.com/index.html

➡️ AppBuilder : allanon71.itch.io/appbuilder

#programming #buildtools #multiplatform #crosscompiling

Screenshot of my app called AppBuilder, the main window is composed by several areas where you can select the target architectures and the plugins you app has to use.
a pile of mosstodd@spacelase.rs
2024-02-03

I started nerd blogging. I would say "again" but even in my 25 years of occasional blogging, I've never written about coding or technology except for brief asides or single posts.

Anyway, today's post is about #rust and #crosscompiling for many targets and how to do it.

blog.selfassembled.org/cross-c

I also wrote the static site generator for this blog (its the same one my oft-neglected cooking blog whatever.todds.cooking uses) and it's written (poorly) in Rust as well (it was my 1st Rust project)

2024-01-22

I wish #CrossCompiling some open source projects hadn't devolved to some combination of #QEMU and #Docker

It is so much faster to use a cross-build toolchain running on your host machine! Even if you run that in Docker!

Edit: I'm not owned, I'm not owned! users.rust-lang.org/t/cross-co

2023-12-20

Why do some target triples contain -pc after the machine architecture?
#crosscompiling

Adam Sjøgren's blogblog@koldfront.dk
2023-12-17

Cross compiling for OpenWrt/LEDE mips_24kc_nomips16

Recently I looked at OpenWrt's list of recommended hardware and when I to my surprise saw an access point available in local webshops on the list, a Xiaomi AX3200, I treated myself to one.

What I didn't think to check was whether the new access point has a usb port.

It doesn't.

Why does that matter? Well, I have this setup where when I tell my computer to print something, it tells the access point to toggle a usb controlled relay, which turns on the printer.

It's pretty neat, if I may say so myself.

However switching from the old access point to the new would leave me without somewhere to plugin and control the usb relay.

But wait, the Genexis Pure ED500 VDSL router I have that connects to the internet, it has a usb port, and it runs a customized version of OpenWrt, maybe I can use that?

Unfortunately it runs a veeery old version of OpenWrt:

* iopsysWRT Version    = 4.3.6 * LEDE/OpenWRT Version = Reboot (SNAPSHOT, r0+8411-adc4ef5) * Linux Kernel Version = 4.9.109+ 

running opkg update on it just gave a whole bunch of "404 Not found". And I need the crelay package.

After searching for a while, I couldn't find it anywhere online. I could find one build for mips_24kc, but not for mips_24kc_nomips16 - there are very few hits for "nomips16".

I tried the package for mips_24kc any way, and after installing the needed libraries: "Bus error".

Ok, so I probably need to (cross) compile it myself. I posted a cry for help on the fediverse, but there were no takers.

Armed with the information from /etc/openwrt_release:

DISTRIB_ID='LEDE' DISTRIB_RELEASE='SNAPSHOT' DISTRIB_REVISION='r0+8411-adc4ef5' DISTRIB_CODENAME='reboot' DISTRIB_TARGET='intel_mips/xrx500' DISTRIB_ARCH='mips_24kc_nomips16' DISTRIB_DESCRIPTION='LEDE Reboot SNAPSHOT r0+8411-adc4ef5' DISTRIB_TAINTS='no-all busybox override' 

I went searching again, and I found a guide "Cross compiling" on the OpenWrt website, which says to start by setting up the build system as described on "Build system usage".

After a couple of false starts, this is what I did:

  • Checked out the lede-17.01 branch
  • In make menuconfig choose the architechture that looked like it might be mips_24kc, switched to big endian, turned on advanced options, turned off mips16.
  • Fixed the various problems in building tools and toolchain:
    • Fixed tools/m4 compilation by removing && SIGSTKSZ < 16384 in c-stack.c.
    • Fixed tools/mklibs compilation by adding HOST_CPPFLAGS += -std=gnu++98 to the Makefile, as seen in "tools/mklibs: Fix compile with GCC 11" on the openwrt-devel mailing list.
    • Fixed toolchain/gcc compilation by adding HOST_CXXFLAGS += -std=gnu++98 and CFLAGS_FOR_TARGET="$(TARGET_CFLAGS)" in common.mk
    • Fixed cmake-3.7.1 compilation by adding #include <limits> in cmStandardIncludes.h as indicated in "‘numeric_limits’ is not a member of ‘std’" on StackOverflow.
  • Followed the instructions on "Building a single package" to build crelay.
  • Unpacked the crelay, libftdi1, and hidapi ipk's and copied the files to the router.

Success!

Now I can switch from the old access point to the new, and still have printing working as smoothly as before.

2023-12-15

Any tips for cross compiling on amd64 targeting mips_24kc_nomips16?

I want to install crelay on a Genexis ED-500 router, which is running LEDE/OpenWrt "Reboot" (snapshot) from waaaay back.

Currently I have crelay running on a Netgear R6350, but I'd like to switch to another access point which unfortunately does not have a USB port, so I want crelay on the router.

So, what is the easiest way to compile for Windows for Linux users? I have used Linux exclusively for the last six or seven years and I really don’t want to have to mess around with dual booting…but I would like to be able to build and send things to friends. I think my best bet is probably a VM, but I’m wondering if there are any reasonable cloud services I can use.
#crosscompiling #linux #windows

2021-01-21

Just tried out #crosscompiling with #Nix. It's actually this simple:

nix-build '<nixpkgs>' -A pkgsCross.riscv64.hello

file /nix/store/XXX-hello-2.10-riscv64-unknown-linux-gnu/bin/hello
ELF 64-bit LSB executable, UCB RISC-V, version 1 (SYSV), dynamically linked ...

nix-build -A pkgsCross.mingwW64.hello

file /nix/store/XXX-hello-2.10-x86_64-w64-mingw32/bin/hello.exe
PE32+ executable (console) x86-64 (stripped to external PDB), for MS Windows

not tested to run these

#NixOS #nixpkgs #linux

2018-07-08

15:00 / Platane - A13 :
(FR/EN) Atelier / Workshop :

Installing and using the #NetSurf #toolchains
#Crosscompiling for ☑ #Atari #MiNT, ☑ #Amiga #AmigaOS, ☑ #RISCOS… ☐ NeXT ?

2018.rmll.info/fr/program/cale

#oldschool #retrocomputing #RMLL #RMLL2018

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst