Skip to main content
This guide will help you contribute to the Android NDK, whether by reporting issues or submitting patches.

​
Reporting issues

Our bug tracker is hosted on GitHub Issues.
Bugs against Android Studio or Gradle should be filed at b.android.com, not in the NDK issue tracker.
Before filing a bug, check that you are using the latest version of the NDK. The latest stable version and the preview release of the next stable version are listed on the NDK wiki.

​
Submitting patches

While we use GitHub for bug tracking and documentation, we do not manage our code in GitHub. Like the rest of Android, we are hosted in AOSP. This means that patches are uploaded to and submitted via Gerrit.
1

Follow AOSP contribution instructions

Follow the contribution instructions for AOSP.
2

Initialize the repository

When you run repo init, follow the instructions in the NDK README.md. The NDK has a different set of dependencies than AOSP.
3

Build and test

Instructions for building the NDK and running tests are documented in README.md and Testing.md.
The NDK cannot be built on Windows; only Linux and Darwin hosts are supported.
4

Upload your change to Gerrit

Upload your patch to Gerrit following the AOSP workflow.
5

Find reviewers

Use the [FIND OWNERS] button in the Gerrit UI to find appropriate reviewers for your change.
6

Wait for presubmit checks

The NDK uses TreeHugger as a presubmit service (similar to CI/CD for Gerrit).
  • If you’re a Googler, TreeHugger will check your change automatically when you upload it
  • If you’re not a Googler, you’ll need to get a Googler to approve the change before TreeHugger will run it

​
Resources

Build docs developers (and LLMs) love

Get started for freeTalk to us