Arch Linux

sshaikh

Member

Registered: 2019-07-03

Posts: 64

[SOLVED] Cross Compiling an ARM project?

I'm trying to build https://github.com/ljalves/hfeasy.

My first step was to install the arm-none-eabi-gcc package as the makefile seems to require this.

I then updated the Makefile.mk by setting `GCC_PATH=/usr`.

This gives me the following error:

In file included from hfeasy.h:4,
                 from app_main.c:24:
/home/user/projects/hfeasy/hfeasy/sdk/4.13/include/hsf/hsf.h:19:10: fatal error: stdio.h: No such file or directory
   19 | #include <stdio.h>
      |          ^~~~~~~~~

I tried adding /usr/arm-none-eabi/include/c++/14.2.0/tr1/ and others to the INCLUDE path in the Makefile which allowed me to progress to a point, but then I get various type errors which leads me to believe that I'm chasing the wrong rabbit.

The module is this one: http://www.hi-flying.com/hf-lpb100. I have also tried downloading the SDK from there but it doesn't appear to have any further files than what was available in the repo. I suspect I'm missing some kind of general build package but I have glib installed so wonder how to determine what else is required.

Last edited by sshaikh (2024-12-09 21:44:29)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,038

Re: [SOLVED] Cross Compiling an ARM project?

GCC_PATH=/opt/gcc-arm-none-eabi-7-2018-q2-update

You may need an older version of gcc-arm-none-eabi .

Try the PKGBUILD at https://aur.archlinux.org/cgit/aur.git/ … 8ccff183e7

It's from 2018 so no idea if it will still work.

Last edited by Lone_Wolf (2024-12-09 11:23:07)

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

sshaikh

Member

Registered: 2019-07-03

Posts: 64

Re: [SOLVED] Cross Compiling an ARM project?

This worked! Many thanks!

Well, at least up to a point - looking more closely it seems that the repo moved on from Makefiles and started building in uvision (Windows) instead. The project files there appear to be more up to date. I may try to have this build in Linux again in the future but for now I'll try via uVision (remembering the lesson here that it's important to recreate the same dev environment used for an older repo)