1. 27 Jul, 2016 1 commit
    • Dan Albert's avatar
      Document the new platform API process. · f2db125b
      Dan Albert authored
      We're moving the header/library generation part of the NDK build into
      the platform build. A number of reasons for this:
      
      1. Simplifies the NDK API development process by removing the need to
         build the full NDK to test your API. NDK APIs can now be tested by
         CTS the moment they are written rather than needing to wait for a
         new NDK to be dropped into prebuilts/ndk.
      2. Allows NDK APIs to be developed in release branches rather than
         AOSP. Right now if we want to avoid announcing an API we have to
         avoid putting it in the NDK until its ready.
      3. Keeps the NDK headers and the platform headers from getting out of
         sync. Right now framework headers are only updated when someone
         remembers to update them, and the libc/libm headers were forked
         from bionic years ago, and then again for L.
      
      Test: None
      Bug: http://b/27533932
      Change-Id: Ie0bf325bba627630d55837ddb3094ea487c41490
      f2db125b
  2. 06 Jul, 2016 1 commit
    • Dan Albert's avatar
      Correct our docs regarding adding platform APIs. · ba10626c
      Dan Albert authored
      This section was really misleading if you were updating an existing
      library. Since that is likely the norm, clarify that the old symbol
      lists need to be copied over rather than starting with a fresh file.
      
      Change-Id: Ic2dd8d29a86a680f0afd5611dd5ac623542f152f
      ba10626c
  3. 06 Apr, 2016 1 commit
  4. 10 Feb, 2016 1 commit
    • Dan Albert's avatar
      Add documentation about out convoluted sysroots. · af921c44
      Dan Albert authored
      I've answered the question of how to add new native frameworks APIS
      several times in the past week, so I've finally taken the time to
      write it all down.
      
      Change-Id: Ic828ede2f1de5b29e283306ff0264ac2e469d70d
      af921c44