# Compilation for arm64/aarch64

**URL:** <https://discuss.px4.io/t/compilation-for-arm64-aarch64/29179>\
**Category:** Development\
**Created:** [September 27, 2022, 11:19am UTC](https://discuss.px4.io/t/compilation-for-arm64-aarch64/29179 "2022-09-27T11:19:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jurstu](https://discuss.px4.io/letter_avatar_proxy/v4/letter/j/a9adbd/32.png) [@jurstu](https://discuss.px4.io/u/jurstu)\
**Post date:** [September 27, 2022, 11:19am UTC](https://discuss.px4.io/t/compilation-for-arm64-aarch64/29179/1 "2022-09-27T11:19:43Z")

</div>

Hello,

I am developing a product using QGC and will modify it later, but now I want to compile a normal QGC version from:

> **[GitHub - mavlink/qgroundcontrol: Cross-platform ground control station for...](https://github.com/mavlink/qgroundcontrol)**
>
> Cross-platform ground control station for drones (Android, iOS, Mac OS, Linux, Windows) - GitHub - mavlink/qgroundcontrol: Cross-platform ground control station for drones (Android, iOS, Mac OS, Li...

and I’m following instructions to compile  
a) with docker  
b) with QT installed natively.

The problem is that I’m trying to do it on an architecture described below:

Plaftofm: IMX8 cortex A53,

uname -a output:  
`Linux iWave-G40M 5.15.5-lts-next+gaffb3e2d0847 #1 SMP PREEMPT Tue Jul 26 09:45:54 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux`

qt5.15.2: compiled from source according to:  
[https://wiki.qt.io/Building\_Qt\_5\_from\_Git](https://wiki.qt.io/Building_Qt_5_from_Git)

b)

making (make -j4) allowed me to go the same error as here:

> <https://github.com/carlonluca/docker-qt/issues/1>
>
> I want qt5.15.2 to compile the latest qgc and then run it on arm-based ubuntu20.…04, which aontainer is what I need?

which was:  
`cp: cannot stat '/opt/Qt-arm64-5.15.2/lib/libicui18n.so*': No such file or directory`

I was able to overcome it by installing libicui18n.so (of some kind). It fixed the error at the end of make, but didn’t allow me to run QGC with success (the window opened, but everything was black [wayland, ubuntu 20]

But I feel like each of my solutions is a weird workaround.

a) I managed to come to same error using docker container, but didn’t manage to get past libicui problem.

I don’t really want to keep trying on this installation because tbh it feels like hell.  
I want to reinstall the system (ubuntu 20) and check if the “correct way” of installing everything would work.

My question is how to setup build env for aarch64/arm64 the “correct way”?

---

<div class="post-metadata">

**Author:** ![AliceJin908](https://discuss.px4.io/user_avatar/discuss.px4.io/alicejin908/32/15750_2.png) [@AliceJin908](https://discuss.px4.io/u/AliceJin908)\
**Post date:** [February 27, 2024, 9:10am UTC](https://discuss.px4.io/t/compilation-for-arm64-aarch64/29179/2 "2024-02-27T09:10:40Z")

</div>

need the answer for the same question! I need to compile a QGC executable file for arm-based device(on OS: Ubuntu 22.04.3 LTS).