Mobile and Embedded

AFAIK, yes, but you have to deploy it as well.

Hi, As the error states: use Java 1.8 use a NDK that matches Qt's recommendations. Latest and greatest is rarely a good idea as they have a tendency to change stuff without warning and break workflows.

Hi All, When I am compiling my Qt app, I am getting the same problem, Please did you solve it? [image: 2878fce3-6697-4e1c-b2d1-5d1b8ce163d3.png] link text

On a fresh VM with QT installed the project works fine. On bare-bone even a QT-reinstall did not help, any idea what might be going on? Any ideas on what to 'wipe out' (besides doing a fresh QT-reinstall) are welcome so to make GDB work again. The project's settings are same across bare-bone and VM. That is strange is it not. Couple of other strange things: both on VM and bare-bone QT decides to use a wrong debugger by default (from a different NDK than the compiler). Debuggers for previous NDKs are not even listed by default one has to include them by hand (even though QT wanted the two NDKs downloaded)

@Vega4 said in Choose NDK version for Qmake: We do not want to recompile the entire internal toolchain(libraries) just because Qt suddenly feels like doing so I did not say you have to rebuild the tool chain, rebuild your Android app.

Installing and running an X11 server resolved my issue thanks!!!

It is documented in "detailed description" of the class. But you are right, it should also be mentioned as a property in the list of properties - that's a documentation bug, please report it.

Hi Folks.... was calling the setFlags wrong. this is the code I ended up with and working (tho no error checking atm) QAndroidJniObject path=QAndroidJniObject::fromString("content://blahSuiteQL.fileprovider/mypdf/" + tmpStra); QAndroidJniObject jniUri = QAndroidJniObject::callStaticObjectMethod("android/net/Uri", "parse", "(Ljava/lang/String;)Landroid/net/Uri;", path.object<jstring>()); QAndroidJniObject jniParam = QAndroidJniObject::getStaticObjectField<jstring>("android/content/Intent", "ACTION_VIEW"); QAndroidJniObject intent("android/content/Intent","()V"); intent.callObjectMethod("setAction","(Ljava/lang/String;)Landroid/content/Intent;",jniParam.object<jstring>()); QAndroidJniObject jniType = QAndroidJniObject::fromString("application/pdf"); jint jniPermissions = QAndroidJniObject::getStaticField<jint>("android/content/Intent","FLAG_GRANT_READ_URI_PERMISSION"); intent.callObjectMethod("setFlags", "(I)Landroid/content/Intent;",jniPermissions); intent.callObjectMethod("setDataAndType", "(Landroid/net/Uri;Ljava/lang/String;)Landroid/content/Intent;", jniUri.object<jobject>(), jniType.object<jstring>()); QAndroidJniObject activity = QtAndroid::androidActivity(); QAndroidJniObject packageManager = activity.callObjectMethod("getPackageManager","()Landroid/content/pm/PackageManager;"); intent.callObjectMethod("resolveActivity","(Landroid/content/pm/PackageManager;)Landroid/content/ComponentName;",packageManager.object()); QtAndroid::startActivity(intent, 0); Kind Regards Craig

I did a quick google for the Qt LGPL license. Currently, Qt seems to have proper instructions which will not bully you into buying a commercial license instead: https://www.qt.io/faq/3.7.-what-are-my-obligations-when-using-qt-under-the-lgpl As the link states you have to be careful which modules you use. There are a few modules which are only available under GPL or commercial license. Usually, this should not be a problem. If you link dynamically with Qt you only have to make your users aware of their rights (state that your software uses Qt under LGPL v3 and provide the actual text of the LGPL v3) and make the source code of Qt available to them (you don't have to make your own source code available). The latter can be done in two ways: 1) You can make Qt source available in the same way as your software (e.g. if you distribute your software via download, you can host the Qt source at the same location) or 2) make a written offer (valid for at least 3 months IIRC) to everybody who gets your software to request Qt's source code from you. If you link statically with Qt you have to provide users with instructions and tools so they can relink with a different Qt version. On desktops this would most often mean you have to distribute your object files (of your own software) with instructions how to link them to Qt.

The solution is setting the environment variable QT_GPA_PLATFORM = linuxfb:fb=/dev/fb0.

@m2dtkast does your build.gradle contain dependencies { implementation fileTree(dir: 'libs', include: ['*.jar', '*.aar']) compile 'com.android.support:support-v4:25.3.1' }

@jsulm Thank you.

@Marek-Belisko I already gave you a hint.

@TheCrowKaka Yes, we now have the same solution running on Windows desktop, Android and iOS, basicly using this method: https://www.kdab.com/efficient-barcode-scanning-qzxing/