I feel your pain about Eclipse.
Google Play services just recently was split into multiple libraries.
Assuming you don't need Google Games and Google Wear and Google Fitness and
Google Helicopters and Google Sandwiches and Google Wallet and Google
Kitchen Sink all at the same time -- you should be able to include just the
ones you need.
You can find them under:
<sdk root>/extras/google/m2repository/com/google/android/gms/
This is part of "... something ... Repository" in the SDK Manager.
Now, those are .aar files, but they're simple archives -- you should be
able to the contents and use it as an Eclipse library project:
unzip -l play-services-wearable-6.1.71.aar
Archive: play-services-wearable-6.1.71.aar
Length Date Time Name
--------- ---------- ----- ----
5763 2014-10-08 22:05 R.txt
1088 2014-10-08 22:05 AndroidManifest.xml
1356943 2014-10-08 22:05 classes.jar
0 2014-10-08 22:05 res/
0 2014-09-25 19:07 res/values-bg/
5350 2014-09-25 19:07 res/values-bg/common_strings.xml
0 2014-09-25 19:07 res/drawable-tvdpi/
823 2014-09-25 19:07
res/drawable-tvdpi/ic_plusone_medium_off_client.png
828 2014-09-25 19:07
res/drawable-tvdpi/ic_plusone_small_off_client.png
874 2014-09-25 19:07
res/drawable-tvdpi/ic_plusone_standard_off_client.png
873 2014-09-25 19:07
res/drawable-tvdpi/ic_plusone_tall_off_client.png
...
Should work, although I haven't done this.
What I have done, and it worked -- needing just OAUTH stuff, before this
split happened -- was to:
- use the Eclipse project for Play Services under:
/home/kman/Android/android-sdk-linux/extras/google/google_play_services/libproject/google-play-services_lib/libs
- extract the monolithic google-play-services.jar and repackage just the
files I needed into a new .jar and using that one instead
- carefully delete unused resources (languages that my app doesn't have
translations for anyway, a bunch of images...)
-- K
2014-12-17 23:22 GMT+03:00 Nathan <[email protected]>:
>
> I was wondering what all the fuss was over the Dex limit, till I included
> Google Play Services.
>
> Right away, I got the dreaded error:
>
> Conversion to Dalvik format failed:
> Unable to execute dex: method ID not in [0, 0xffff]: 65536
>
> So now I am referring to the official guide:
>
> Building Apps with Over 65K Methods:
> https://developer.android.com/tools/building/multidex.html
>
> It says, I think, that on Android 5.0 I will be fine.
> Good so far.
> On pre 5.0, use the multidex support library.
> Okay, so I included android-support-multidex.jar in libs folder.
>
> The next section is
> Configuring Your App for Multidex with Gradle
> Hmm, no section for Configuring Your App for Multidex with ADT/Eclipse
> They weren't kidding about dropping support for ADT like a rock.
>
> A colleague found this
>
> http://stackoverflow.com/questions/13439882/android-error-in-eclipse-unable-to-execute-dex-cannot-merge-new-index-65799-i
> Suggesting that we should use
> dex.force.jumbo=true
> in each project.properties.
> It seemed to work for him
> I don't know if this applies to the android libraries like appcompat and
> Google Play Services.
>
> I tried it. Didn't help.
> Still getting this when I try to debug:
>
> Conversion to Dalvik format failed:
> Unable to execute dex: method ID not in [0, 0xffff]: 65536
>
> Saw this article too:
>
> http://android-developers.blogspot.com/2014/12/google-play-services-and-dex-method.html
> Hmm, these instructions are also only for Gradle. No way to do it in ADT?
>
> So my questions are:
> *Can I get around this in ADT/Eclipse or should I speed up the migration
> to Android Studio. ? *
>
> I see this note at the bottom:
>
> *Note:* Use of multidex for creating a test APK is not currently
> supported
>
> Does this mean no more debugging my code?
> Just ship it to Google Play and hope for the best?
> We are all Klingon warriors now - we do not debug - our software does not
> coddle the weak. ;)
>
> Nathan
>
>
>
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
