4

We all know Android Support Library has bugs. Some of them trivial and not fixed for years. I need to fix a few of them, but... how do I compile ASL source into usable JAR?

ssuukk
  • 8,200
  • 7
  • 35
  • 47
  • What I did until now - in Eclipse created a directory in which I've put all classes from support library source. I added android.jar to the project and it doesn't show any errors after this. Then I used "Export..." into jar, which finished with some warnings and a size very close to ariginal android-support-v13.jar. Unfortunately my Android application with this self-built library fails with lots of missing classes reported at runtime (meaning it compiles without a problem). – ssuukk Jun 21 '13 at 08:27
  • If you are using Eclipse with the R22 tools, be sure you have fixed the "Order & Export" portion of your build path: http://stackoverflow.com/questions/16596969/libraries-do-not-get-added-to-apk-anymore-after-upgrade-to-adt-22/16596990#16596990 – CommonsWare Jun 21 '13 at 10:46
  • Hmm... I've got only JRE Sytem library and android.jar in that tab in my support library project. I've created this project as Java, not Android. Do you know proper steps to make it Android compatible? – ssuukk Jun 21 '13 at 10:55
  • I'd make it an Android project. The JRE library is not going to do you any favors. Just because you aren't creating an app doesn't preclude you from making it an Android project -- makers of reusable Android components do this all the time. – CommonsWare Jun 21 '13 at 11:10
  • Nope. Same result. Builds well, but at runtime fails with unresolved classes, interestingly the classes are independent of the support library. – ssuukk Jun 22 '13 at 06:38

0 Answers0