I’m currently trying to cross-compile HailoRT for OpenWrt and get it running properly on my setup — but I’ve hit a few roadblocks that I can’t seem to get past.
I’ve gone through the docs and tried multiple build configurations, but I’m running into dependency issues and some weird recursive config problems while building. Before I go too deep into trial-and-error, I’d really appreciate some pointers from anyone who’s managed to:
Cross-compile HailoRT successfully for OpenWrt
Integrate it with the OpenWrt build system or SDK
Or get it running cleanly on an embedded target
Any tips, patches, or example configs would be super helpful right now — I’m trying to get this working ASAP.
Thanks in advance to anyone who can share some insight
We don’t have official support for OpenWrt, but hopefully someone here has tried it and can chime in. Here’s what I’d focus on for the compilation process:
The main thing is getting your toolchain set up properly. You’ll need to create a CMake toolchain file for your OpenWrt target (similar to how it’s done for Yocto). Your build commands would look something like:
Your toolchain file should define things like your cross-compiler paths, sysroot, and system processor architecture. You can look at the Yocto/ARM examples in the docs as a template and adapt them for your OpenWrt SDK.
Hope this helps! Let me know if you run into any issues. If the compilation problems continue, could you share some of the error logs? That would help me troubleshoot better.
I was able to get HailoRT running on OpenWrt (Banana Pi R4 / Filogic) — posting this in case it helps others. You can either use the OpenWrt SDK or clone the full OpenWrt repo and add HailoRT as a custom package under package/. I used a Makefile to pull and build the HailoRT source directly from GitHub, linking dependencies like libstdcpp, libpthread, and libusb-1.0.
Once the target system (MediaTek ARM → Filogic) is set in menuconfig, the build produces a working .ipk that installs cleanly on the device.
I ran into some hash mismatches, toolchain setup issues, and SCP transfer quirks along the way, but all solvable with minor adjustments.