{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibmf627ep7u6xiron6m54hcd3kgse2igidnq3ofuu4c2euxvcbeyu",
    "uri": "at://did:plc:34cg4tn4iwemk3v5k3n3adwf/app.bsky.feed.post/3mfs5phlauz22"
  },
  "path": "/t/open-source-android-development-tools/30599?page=9#post_183",
  "publishedAt": "2026-02-26T21:15:55.000Z",
  "site": "https://forum.f-droid.org",
  "tags": [
    "https://codeberg.org/Starfish/SDK-Rebuilds/src/branch/main/how_to_use.md"
  ],
  "textContent": "Okay, first of all, I don’t know how people feel about double posting here. I didn’t want to add a big edit to the last, but I’m worried I’m making a faux pas here. I hope this is okay…\n\nSome updates: the latest SDK 15 (r36) has been built without containing the EULA. But I’m having trouble with SDK 16 (r4) I’m getting `Too many open files (os error 24)` despite increasing the limit by both ulimit and by editing my /etc/security/limits.conf. I will dig deeper into this when I have some more time. Maybe r4 is just broken or I’m having too many cores causing too many parallel jobs?\n\nApart from this, I saw the file `repository.xml` in the build output. It seems (and according to the work of Beuc) to be an old solution for package hosting metadata. The point is, it had a nice naming for the files: no versions at all, so just remove the “-username” from the end of the file. So to answer my previous pondering, I’m now going with “android-sdk_linux-x86.zip”, “sdk-repo-linux-build-tools.zip” and similar. I’ve also cleaned up most of the code and added an EULA scanner script, so every time a build finishes the results are checked for traces of it (it can also be used directly to check files).\n\nSome more exciting news! It seems Starfish on codeberg has continued to work on their SDK rebuild solution, and have just posted a guide on how to actually use the custom built files for normal (unmodified gradle) builds: https://codeberg.org/Starfish/SDK-Rebuilds/src/branch/main/how_to_use.md. This seems important, I was wondering how to do this (although my own project doesn’t need it). Maybe I should reach out and see if our effort could be combined?",
  "title": "Open Source Android Development Tools"
}