Mobile and Embedded

@Kyeiv said in Could not resolve all artifacts for configuration ':classpath': OpenJDK 9.0.4 You need to use Java 8, see here. Versions higher than 8 might cause issues for the Android SDK command-line tools.

I don't understand this well: From looking at the documentation, it seems that the QAndroidJniObject constructor and methods have to be attaching and detaching the current thread to and from the JVM, which isn't going to work in a JNI thread that's already attached to the JVM. Does this mean that, if I call C++ function(that uses QAndroidJniObject) from java JNI class, it is not going to work? Because as I understand, QAndroidJniObject is attaching and detaching the current thread to and from the JVM, and the JNI java object that is calling native functions, is already attached to the JVM. Please correct me if I am wrong.

I thought the same way at first, but I thought maybe I did the wrong way and couldn't optimize the code.So now I have to find another timer function for my code.Thank you,nice a good day!

Nevermind, solved, removed unncecessary assignment RCC_DIR = $${OUT_PWD}/rcc in old project .pro file.

Hi, I have not used that but my guess would to just set the path as you would for using anything stored in Qt's ressource system.

Thank you I will report it

@Pablo-J-Rogina Thanks for replying :-> Yesterday I figured out what the problem was: Had a problem with opengl and the sgx graphics driver. But now it works perfectly

Please note https://bugreports.qt.io/browse/QTBUG-76411, as Android 8 and later have quite a few new restrictions to background services.

Just wanted to say thanks! I ran into the same issue (building qtwebengine) on Ubuntu 18.04 host and this fixed it. I'm adding it to my personal list of prerequisites for my Boot2Qt Yocto builds....

Well I guess there is no other option, I opened the ticket, can only hope it gets actually fixed or for a workaround.

@williamsk Ah, cool. So as your problem is solved, please mark this topic as SOLVED too (button Topic Tools). Thanks and regards

@SGaist Attached is the minimal compilable example project showing the issue. Incase unable to view the example, attached the same project in https://bugreports.qt.io/browse/QTBUG-87742 Ensure Qt 5.6.3 is installed in the path /usr/local/Qt-5.6.3. The top level handwritten makefile uses TestQmake.pro to generate Makefile_g in the current directory but not in sub-directory unlike Qt 4.8. Makefile_g: $(PRO_FILE_NAME) $(QMAKEPATH)qmake -o $@ $(QMAKESPEC_SWITCH) $(QMAKESPEC) $< To build the example project: cd TestQmake make clean make all Expected: The makefile in subdirectory testwidget should be generated with filename "Makefile_g" Actual: The makefile in subdirectory testwidget is generated with filename "Makefile"

@Andreamem Hi and welcome to the open source devnet forum Since you have a commercial license you are entitled to get also the commercial assistance. They can tell you also what you are required to do. The open source folks are not likely to know such legal details.

@jsulm said in HEIC Image Conversion? Is it possible?: @Ramport said in HEIC Image Conversion? Is it possible?: Heic only supports IOS devices This is wrong, see "Support" and "Operating systems" https://en.wikipedia.org/wiki/High_Efficiency_Image_File_Format https://www.iseepassword.com/convert-heic-to-jpg.html Thank you,but that i also added what I got here,you can convert between Heic and JPG at will, but Heic pictures cannot be supported on Windows devices unless they are converted to JPG pictures.