1. 03 Jul, 2020 4 commits
  2. 02 Jul, 2020 1 commit
  3. 01 Jul, 2020 1 commit
  4. 28 Jun, 2020 5 commits
  5. 21 Jun, 2020 1 commit
  6. 20 Jun, 2020 1 commit
  7. 18 Jun, 2020 2 commits
  8. 17 Jun, 2020 2 commits
  9. 14 Jun, 2020 1 commit
  10. 11 Jun, 2020 1 commit
  11. 04 Jun, 2020 2 commits
  12. 02 Jun, 2020 2 commits
  13. 09 May, 2020 1 commit
  14. 08 May, 2020 3 commits
  15. 07 May, 2020 2 commits
  16. 04 May, 2020 1 commit
  17. 01 May, 2020 1 commit
  18. 24 Apr, 2020 1 commit
    • Nicolas Fella's avatar
      Initial check for invalid JNI method signatures · 579779bd
      Nicolas Fella authored
      Summary:
      When using QAndroidJniObject to call Android API one needs to specify method signatures using strings. This is error-prone and errors are usually only detected at runtime.
      This check searches for a set of known methods that take such signatures and validates them using a regular expression. If a signature is invalid a warning is emitted.
      
      To be able to verify Android-specific code with a desktop clang we need some include path hackery. QAndroidJniObject required jni.h, which is shipped in the Android NDK. We therefore need to amend the include paths. In order to do that we rely on $ANDROID_NDK being set and print an error if not.
      
      Test Plan: Ran tests
      
      Reviewers: smartins
      
      Reviewed By: smartins
      
      Differential Revision: https://phabricator.kde.org/D28887
      579779bd
  19. 19 Apr, 2020 4 commits
  20. 14 Apr, 2020 2 commits
  21. 13 Apr, 2020 1 commit
  22. 06 Apr, 2020 1 commit