compileSdkVersion和targetSdkVersion的区别

最新推荐文章于 2025-04-07 15:34:58 发布

原创最新推荐文章于 2025-04-07 15:34:58 发布 · 1.2k 阅读

0 ·

CC 4.0 BY-SA版权

Android 专栏收录该内容

68 篇文章

订阅专栏

本文解析了Android开发中compileSdkVersion与targetSdkVersion的区别：前者决定应用编译时支持的API版本，后者指示应用已针对哪个版本进行了测试。深入探讨了这两个属性如何影响应用的功能使用及运行时的表现。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

直接粘一段老外的内容。

compileSdkVersion

The compileSdkVersion is the version of the API the app is compiled against. This means you can use Android API features included in that version of the API (as well as all previous versions, obviously). If you try and use API 16 features but set compileSdkVersion to 15, you will get a compilation error. If you set compileSdkVersion to 16 you can still run the app on a API 15 device as long as your app's execution paths do not attempt to invoke any APIs specific to API 16.

targetSdkVersion

The targetSdkVersion has nothing to do with how your app is compiled or what APIs you can utilize. The targetSdkVersion is supposed to indicate that you have tested your app on (presumably up to and including) the version you specify. This is more like a certification or sign off you are giving the Android OS as a hint to how it should handle your app in terms of OS features.

For example, as the documentation states:

For example, setting this value to "11" or higher allows the system to apply a new default theme (Holo) to your app when running on Android 3.0 or higher...

The Android OS, at runtime, may change how your app is stylized or otherwise executed in the context of the OS based on this value. There are a few other known examples that are influenced by this value and that list is likely to only increase over time.

For all practical purposes, most apps are going to want to set targetSdkVersion to the latest released version of the API. This will ensure your app looks as good as possible on the most recent Android devices. If you do not specify the targetSdkVersion, it defaults to the minSdkVersion.