Qt's iOS port allows you to run Qt applications on iOS devices, such as iPhones, iPads, and iPod Touches , run qmake > open the resulting . xcodeproj file in Xcode > build the application in Xcode tellpopeyes
ok, still don't know what exactly are unstripped / stripped libs are,
but I managed to get basic NDK reports running :D
the mentioned gradlew app:uploadCrashlyticsSymbol goes into the build.gradle file within the android tag:
other settings can be taken from the official sdk documentation found here
@dxvx said in Init new Android project:
when qtcreator tries to create the gradle and android template, it fails because there is no template in the android SDK
Possibly Google changed the layout again. Sorry, I don't know how to fix this, last time I tried creating templates it worked fine. Make sure you're using the newest Qt Creator and if it persists, please report a bug on Qt bug tracker.
After some analysis it turned out that assets are updated correctly. The fault was in QML cache - it was preserving old data between application runs and even versions. Our current solution is to clear application cache in every startup.
@cano said in Not able to compile "qgroundcontrol" on windows 64 bit:
Project ERROR: Cannot run target compiler ‘C:\Users\Neha\AppData\Local\Android\Sdk\ndk\21.0.6113669/toolchains/arm-linux-androideabi-4.9/prebuilt/windows-x86_64/bin/arm-linux-androideabi-g++’. Output:
Two things here, clearly the compiler cannot run and you didn't paste the whole error message
From the link you posted, instructions call for using Qt 5.7.1 "Make sure to install Qt version 5.7.1 NOT 5.4.x, 5.6.x, 5.8.x, etc."
I'm not sure if that will make a difference...
@Hitokage I would suggest taking a look at this blog post:
It is a rather in-depth post with working code that sends and receives files. It's not perfect but very good, you should be able to adapt it easily enough 😉
I have to build my C++ with Android Studio with the needed ABI
then import this *.so LIB into QT
Yes, copy them to the proper location (depending on the ABI platform) in your Qt project folder structure, so Qt Creator finds it and deploys to the Android device without any issue, i.e.:
no need to create any JNI interface, this is all done by QT
I don't think so. I guess you still need to go like you're currently doing.
Thank you for you help! It really sorted out my issue completely.
I install tools + plus i had to move JDK 8 (from 11)
The single one issue i notices during building is
Found corrupted package.xml at C:\Users\user\AppData\Local\Android\sdk\lldb\3.1\package.xml
However building project finished successfully:
BUILD SUCCESSFUL in 3m 29s
25 actionable tasks: 25 executed
Package.xml looks like
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><ns2:repository xmlns:ns2="http://schemas.android.com/repository/android/common/01" xmlns:ns3="http://schemas.android.com/repository/android/generic/01" xmlns:ns4="http://schemas.android.com/sdk/android/repo/addon2/01" xmlns:ns5="http://schemas.android.com/sdk/android/repo/repository2/01" xmlns:ns6="http://schemas.android.com/sdk/android/repo/sys-img2/01"><license id="android-sdk-license" type="text">
org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 460; XML document structures must start and end within the same entity.
That looks strange since xml looks correct.
@Ramakanth said in Qt5.6.3 Cross compile issue for TI AM335x:
Can you let me know any instructions on cross compiling ICU sources
I'm afraid I cannot help here. Not that I've done it myself.
In addition, since you're using Qt 5.6.3 could it be possible that you use QWebEngine (available since 5.6) instead of QWebkit?
I found where was problem.
Add code below before sslsocket init and its work fine with XMLHttpRequest for https.
QSslConfiguration config = QSslConfiguration::defaultConfiguration();
Thank you for your response @mvuori and @Quang-Phu.
I tried @Quang-Phu solution. It is working perfectly fine. When i download the app from play store, i am not seeing any error. It launches normally.
Thank you for your help @Quang-Phu
There should be no problems with adhering to these requirements, iOS 13 SDK is already supported and the guidelines are down to the application itself anyway. If somehow Qt is preventing it then you can file a bug report to get it investigated, or contact Qt support if you have a license.