为什么你会选择在谷歌的API Android的API在Eclipse中SDK？ [英] Why would you choose Android API over Google APIs in the SDK on Eclipse?
问题描述
当您在Eclipse中创建一个Android项目，你必须选择编译与平台。你可以选择17 API（安卓4.2）或谷歌的API（API 17）。
When you create an android project in Eclipse, you have to choose which platform to compile with. You can choose API 17 (Android 4.2) or Google APIs (API 17).
这是我的理解，谷歌的API是API 17（安卓4.2），但有地图库支持和USB打开库。因此，如果谷歌的API是一样的机器人，但更多的功能...你为什么不选择它每次？
From my understanding, Google APIs is API 17 (Android 4.2), but has the maps library support and usb open library. So if Google APIs is the same as Android, but with more features... why wouldn't you choose it everytime?
有一个缺点，以谷歌的API？网上每个教程中，我看到，他们使用API 17（非谷歌的API）。我总是好奇，为什么他们手动，它只是使用一个具有多个在其更改为替代。
Is there a downside to Google APIs? Every tutorial online I see, they use API 17 (Non Google APIs). I'm always curious as to why they manually change it to that instead of just using the one that has more in it.
推荐答案
在运行与谷歌的API，你的应用程序是建立在其上安装有已经（地图，USB等）的谷歌服务的设备上运行。如果你确实需要这些服务，你应该建立针对谷歌的API，但你的应用程序将无法在设备并非由谷歌（也就是不具备谷歌播放设置）。
When you run with Google APIs, your app is built to run on a device which has the Google services installed on it already (Maps, USB etc). If you absolutely require these services, you should build against Google APIs, but then your app will not run on device which aren't certified by Google (that is, don't have Google Play installed).
如果你想在没有谷歌播放设备上运行，并且您的应用程序不需要任何的谷歌服务的是100％present，那么你应该对编译正常的Android的API。
If you do want to run on device without Google Play, and your app does not require any of the Google Services to be 100% present, then you should compile against the normal Android APIs.
请参阅本文档多一点什么谷歌预计，从认证的设备。
See this document for a bit more on what Google expects from certified devices.
这篇关于为什么你会选择在谷歌的API Android的API在Eclipse中SDK？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
