commit | 3da45e19ade21a95bc149c097ef9c58477f1abb5 | [log] [tgz] |
---|---|---|
author | Steve Kondik <steve@cyngn.com> | Thu Sep 08 23:42:38 2016 -0700 |
committer | Steve Kondik <shade@chemlab.org> | Sun Sep 11 13:54:30 2016 -0700 |
tree | 1b7ae0ccb1db03bcc4878ee2c2ede2fe5c212325 | |
parent | 7be730bbf1388c878ee05912f3b3daf9ff619ab8 [diff] |
cmsdk: Untangle internal vs. external dependencies * The public SDK build is currently including AIDLs which are meant to be used for internal purposes only. My assumption is that this particular implementation was done before we split off an "internal" SDK, which is used by the platform itself. * The issue came up when adding an AIDL which has a backing Java data object which was not included. * It should be safe to simply hide this interface. All references to it are hidden already. It is only used for internal purposes and does not change the API. * With the internal dependencies removed from the public SDK, we can completely remove the reference in the makefile. Change-Id: I0515815543feb077ee5e289b9f900e28758c6e98
The Platform SDK provides a set of APIs that give you easy access to a variety of different features within CyanogenMod. The SDK exposes APIs and system level framework access in the Android framework that aren't available in any other distribution.
You can either download from prebuilts hosted on github or pull directly via Gradle.
Our stable releases are mirrored in Maven Central, and you can fetch the current release by setting your build.gradle
dependencies to
dependencies { compile 'org.cyanogenmod:platform.sdk:5.+' }
Within build.gradle
make sure your repositories
list sonatype OSS repos for snapshots
repositories { maven { url "https://oss.sonatype.org/content/repositories/snapshots/" } }
You can target the future
or development
branch by setting your dependencies
for 6.0-SNAPSHOT
dependencies { compile 'org.cyanogenmod:platform.sdk:6.0-SNAPSHOT' }
For further inquiries regarding this project, please reference the wiki.