README.chromium 2.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445
  1. Name: GVR Android SDK
  2. Short Name: gvr
  3. URL: https://github.com/googlevr/gvr-android-sdk
  4. Version: 1.130.0
  5. Date: 1 March 2018
  6. Revision: 233e7fe922a543e0bc55382d64cacd047307d0e7
  7. License: Apache 2.0
  8. License File: LICENSE
  9. Security Critical: yes
  10. Description:
  11. The GVR Android SDK supports both Daydream and Cardboard, including a simple API
  12. used for creating apps inserted into Cardboard viewers, and the more complex API
  13. for supporting Daydream-ready phones and the Daydream controller.
  14. Local Modifications:
  15. - Due to binary size concern, we have decided to use a static shim library
  16. instead of the shared library that comes with this checkout. The static
  17. libraries are downloaded from a public storage through gclient sync.
  18. - For Version 1.10.0, we have two date: 6 Dec 2016 and 10 Feb 2017. The latter
  19. version cherrypick a CL that fix a crash on K and L.
  20. - All JNI calls in the static library also needs to be manually registered. So
  21. we have 3 jni related files. These files were generated by
  22. base/android/jni_generator/jni_generator.py from Java files. Modifications to
  23. these generated files are documented in the files.
  24. - The files generated by jni_generator.py use base::size which is not available
  25. from third_party; std::extent<decltype> was used instead, which is standard C++
  26. and available.
  27. - In order to run automated end-to-end tests on VR features, VR Services
  28. (com.google.vr.vrcore) and in some cases Daydream Home
  29. (com.google.android.vr.home) need to be installed before running tests. These
  30. are downloaded into test-apks/vr_services and test-apks/daydream_home,
  31. respectively. The downloaded APKs are the release APKs that are or were
  32. publicly available via the Play Store.
  33. - In order to run automated end-to-end tests that involve a Daydream controller,
  34. controller_test_api.aar needs to be present. This allows us to send controller
  35. events using broadcasts like a real controller sends them over Bluetooth. The
  36. library is open-sourced similar to the other .aars, but since it's only useful
  37. for Chromium at the moment, it is uploaded to storage instead of to GitHub like
  38. the GVR SDK.