"Fixed" is a big word though, right now it's more of a "hack", and it needs some pollish, so the patch can be submitted to AOSP. I don't want to keep it from you for that long, so my first test build is attached - don't use it in production builds.

Presenting: Fast AAPT - aka FAAPTLately Android development has been getting me down. Slow builds all over the place in many of my app projects, and my PC is blazing fast - it shouldn't all be that slow, even if you're running Eclipse!Working on DSLR Controller has been driving me mad - testing a minor change in the underlying communications library, then building and launching the app - ugh! So I set out to fix this. I had done all the usual tricks, even gave Eclipse loads more memory (helped with regular performance, but not building) but nothing major seemed to change. Then I figured out most of the time building was spent in AAPT. So I synced my AOSP repo (2012.09.26, took a few minutes), tried to get the Windows SDK to build on my Linux box (took several hours) and finally got to actually mucking with the source.Found the bottleneck (for my long-build-time projects at least, related to XML file compilation) and fixed it (by introducing a simple cache). "DLSR Controller" build time has gone down from 35 seconds minimum, to 2-3 seconds ( >10 times faster). Hell, I can even turn "Build Automatically" back on without getting constant delays!Note that my build times quoted only apply to incremental internal builds. If your images still need to be "crushed" (optimized), or you're "exporting" an APK (final build for publication), build time will still be significantly longer. However, during normal development and testing (by far most builds if you're making an app in Eclipse) those stages are not performed, and builds should be lightning fast.Patch code has been submitted to: AOSP - #1 Cancelled, #2 Review in Progress ... superseded by ctate rewrite AOKP - #1 Merged, #2 Merged CM - #1 Cancelled, #2 MergedAttached ZIP includes Linux, Windows and Mac OS X versions.The files are drop-in replacement, but I would certainly advise you to backup the originals for your production builds!Also, don't forget to chmod/chown on Linux or it won't work.Enjoy and leave some feedbackA quick way to spot if this will have effect on your slow build is as follows:- In Eclipse, settounder- Clean and build your project.- If the build pauses on lines in the "" format, you have the problem FAAPT fixes(of course, you can also run aapt manually if you know how, you'll get the same output)In a full framework build the optimizations only affect a very small portion of the actions done during the build, so you won't see any spectaculair speed increases there.I have updated the patch code to fix problems with Mac OS X compatibility, I've also included a Mac OS X binary in the new zip file.-----( v1: 557 )