Mobile and Embedded

I checked and I'm already using NDK-19c. I did find out one more thing: the problem only occurs when signing the apk. This explains why it didn't happen from within QtCreator initially (where I didn't sign) and that it did happen from the command line. The problematic file here is part of the sdk platform-tools/api/annotations.zip and this zip file seems to contain an invalid XML android/accounts/annotations.xml. Apparently, this is an issue in the Google build tools: https://issuetracker.google.com/issues/116182838 Going back to platform-tools 28.0.0 fixed it for me. I've closed this topic for now.

My bad. Sorry for this. Thanks anyway for pointing me to the bug. That's appreciated!

Which version of Qt did you install and how?

Perhaps an issue that should be corrected in the Beta2: https://bugreports.qt.io/browse/QTBUG-79241?jql=project %3D QTBUG AND fixVersion %3D "5.14.0 Beta2"

Hi @JMDY, welcome. How can I get the "vectorcan" QCanBus plugin? What do you mean by that? The vectorcan plugin is included in Qt for Windows with Qt version >= 5.8. Additionally, you'll need the Vector hardware, drivers and library (vxlapi.dll or vxlapi64.dll). Regards

Hi, Any chances that you have non-ascii chars in your user name ?

I just tried with NDK 19 or SDK 29 always same problem. Even QT Example project didn't work, they compile but don't launch with same exception.

Hello @MS_36, Sorry for digging up an old topic. Did you manage to get this working? I mean Crashlytics + QT Android + NDK debug symbols? I've successfully connected my app with Crashlytics, but still I'm unable to upload debug symbols. What's your configuration in build.gradle file? crashlytics { enableNdk true androidNdkOut 'build/intermediates/rs/debug/obj' androidNdkLibsOut 'build/intermediates/jniLibs/debug' manifestPath 'AndroidManifest.xml' } How did you setup androidNdkOut and androidNdkLibsOut variables? Thank you in advance for your response

@Giulio-Dalla-Vecchia said in Cannot get configure script to detect "EGLFS Rasberry Pi": . Hi, Have you got the solution for this?

@Milav said in segmentation fault: the difference between host pc and Embedded target board is only QT source. Host pc => qmake (qt version 5.4.0 ) Embedded target => qmake (qt version 4.8.7) You should have stated these settings from the very beginning... :-) Anyway, could it be possible that you build Qt 4.8.7 for PC (host) and build your example again with that Qt version and run in PC to see what happens.

@crss said in Use Raspberry GPIO via boot2qt: I tried the 'wiringPi' library but I don't know how to insert this on Raspberry Could you share what did you try regarding wiringPi?