Hi, For Qt 6.7 we have made a bunch of changes to the QJniObject class and the so-far-undocumented macros from QtJniTypes. Also, the code structure has changed quite a bit. This change is the diff of the qjni* headers from 6.6 to 6.7:
https://codereview.qt-project.org/c/qt/qtbase/+/524298 If the JNI helpers for Android development are of any interest to you, please join us this Wednesday (Dec 13th) at 13:30 Oslo time for a review of the changes. Here’s the link to the Teams meeting: https://teams.microsoft.com/l/meetup-join/19%3ameeting_OTc0NjU2ZjctN2M1ZC00ODE3LTk2NzctMDVlZTM5ZmZmNWRk%40thread.v2/0?context=%7b%22Tid%22%3a%2220d0b167-794d-448a-9d01-aaeccc1124ac%22%2c%22Oid%22%3a%22de5b241e-f1fd-4127-965f-ca90b3f70722%22%7d Most of the changes are a continuation of the work started for Qt 6.4 and described in https://www.qt.io/blog/unstringifying-android-development-with-qt-6.4 For a bit of JNI code that uses the new Qt 6.7 functionality, check the “fetchFont” helper in https://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/platforms/android/qandroidplatformiconengine.cpp As of now, the QtJniTypes stuff is still undocumented APIs, so one of the questions is whether we are ready to document some of this, and whether we should do that for 6.7 or 6.8. Cheers, Volker -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
