Mobile and Embedded

@Massinissa_idiri said in QT6.6.1 Opengl Cross-Compilation:

wrong architecture detected

Then you're mixing binaries for different architectures.
You will have to provide more information:

Post the actual error message Explain how you're creating the sysroot Show how you build

app is now compiled in debug mode and deployed to tablet. compiling in release mode isn't working.

Hi @Vince_SiriusXM. Did you ever found a fix or workaround for this issue?

i made it myself

as far as I know the Qt Company has always recommended Qt Quick for mobile devices. According to this video, Qt Quick and QML were created because Qt Widgets didn't suit the job of mobile UI.
so your code may work on iOS, I seriously doubt it is intended to.

As far as I know, the intention of the Qt Company, that they've had for long now, is to stop developing new features with Qt Widgets, those new features are available with Qt Quick only. Just have a look at recent modules like Qt Location : it does have UI elements to display maps in Qt Quick / QML, but there's obviously none in Qt Widgets. There's only non UI classes in C++.

By the way, there's a popular tool for UI mockup named Figma that allows you to design your UI, and Qt offers a bridge (which is a Figma plugin, not a Qt Design Studio plugin) that allows you to import your design into Design Studio. (Or use Design Studio directly ? yours to see.)

I'm currently looking at it. It seems really nice.

hi @Axel-Spoerl - sorry it took me so long to respond. I don't see any typos in my code. It turns out that the deployment didn't work because the target directory didn't exist. I created it manually, and got this to work.

Thanks...

@KroMignon being super sassy here as someone who is new to this is trying to understand the landscape. If the system you're deploying to and emulating are both arm, I don't think you would need the google intel x86 system image. that should be for a different type of device.

I ended up switching to QML to solve these issues.

I ended up solving this by using QML instead.

my host machine lists the GLIBC version 2.17 - 2.31 and the g++ -- version is 9.4.0, aarch64-linux-gnu-g++ --version is 9.4.0 and the target board GLIBC versions list from 2.17 -2.36 i was able to cross compile and run my normal c++ projects without any trouble so i don't think the GLIBC versions will be any problem for the qt cross compilation

https://bugreports.qt.io/browse/QTBUG-128829 for what it's worth. I don't understand it yet. But for you, it was working anyway, despite all the warnings?