3 ms·
I don't think these are all necessarily required. At least I would be very very surprised if both avr-libc, mingw, and go were needed.
by matthewbauer 7y ago
I don't think these are all necessarily required. At least I would be very very surprised if both avr-libc, mingw, and go were needed.
- mmastrac 7y agoFor avr-libc, probably this: http://tool.oschina.net/uploads/apidocs/android/guide/topics/usb/adk.html http://tool.oschina.net/uploads/apidocs/android/guide/topics... Unsure about mingw/go, but they are likely deps for some Android ecosystem project.
- jsty 7y agoLooks like go is mostly used in a graphics package (platform_external_skia): https://github.com/search?utf8=%E2%9C%93&q=org%3Aaosp-mirror+language%3AGo&type=Code&ref=advsearch&l=Go&l= https://github.com/search?utf8=%E2%9C%93&q=org%3Aaosp-mirror...
- stusmall 7y agoIt's been something like 3 years since I've worked in AOSP but IIRC mingw is for windows builds of adb. Someone else called out that AVR stuff is for ADK. The Android build tree is more than Android itself. It also builds includes a lot of the supporting tools and libraries for developers.
- ndesaulniers 7y agoFWIW things may not actually be used anymore, doesn't mean the repo is ever taken down. Usually the manifests that sync these repo's simply "unhook" the repos when they're no longer in use. OP is excited that there's a bunch of links, but that's not the correct measure of "in use."