2013-12-18, 01:21
Also I'll try to explain what I was getting at regarding the Android SDK build-tools in a clearer way.
The related steps in the readme are as follows:
It seems that android SDK these days, does not have things like aapt and dx (which xbmc make apk needs) in the platform-tools anymore. They are now in a separate sdk component called build-tools-<version>. For the current SDK the full name of the component is build-tools-19.0.0
So you need to do a to download these.
What I was getting at is, in a future SDK version, presumably this 19.0.0 version may increment. So when documenting this in the readme we cant just say build-tools-19.0.0 as that wont last. You can figure out what the version is, by doing a which gives output similar to:
So from that, we can then see that the package name is build-tools-19.0.0, and can then run the sdk update -u -t <packagename> command
What I was trying to say was, it would be nice if there was a way to download the build-tools-* package, but the android update command doesnt seem to do partial matches in the -t parameter. So the above is how to determine the correct package name and then update it.
Furthermore, XBMC make apk process doesnt understand this new SDK structure, and it tries to run aapt and dx commands, from the SDK/platform-tools location. But they are actually in SDK/build-tools/19.0.0
So until (if) the make script is updated for the new SDK structure, you have to create symliinks for aapt, dx and libs, in the platform-tools area. The symlink commands are in my post above
Hopefully I explained the issues/workaround for getting XBMC make to work with the newer android SDK structure, in a better way this time?
The related steps in the readme are as follows:
Quote:--------------------------------------------------------------------
3.2. Installing Android SDK packages
--------------------------------------------------------------------
After having extracted the Android SDK to <android-sdk> you need to
install some android packages using the Android SDK Manager:
# cd <android-sdk>/tools
# ./android update sdk -u -t platform,platform-tool
It seems that android SDK these days, does not have things like aapt and dx (which xbmc make apk needs) in the platform-tools anymore. They are now in a separate sdk component called build-tools-<version>. For the current SDK the full name of the component is build-tools-19.0.0
So you need to do a
Code:
./android update sdk -u -t build-tools-19.0.0What I was getting at is, in a future SDK version, presumably this 19.0.0 version may increment. So when documenting this in the readme we cant just say build-tools-19.0.0 as that wont last. You can figure out what the version is, by doing a
Code:
./android list sdk --extendedCode:
Packages available for installation or update: 45
----------
id: 1 or "build-tools-19.0.0"
Type: BuildTool
Desc: Android SDK Build-tools, revision 19
----------
id: 2 or "doc-19"
Type: Doc
Desc: Documentation for Android SDK, API 19, revision 1
----------
etc
etcSo from that, we can then see that the package name is build-tools-19.0.0, and can then run the sdk update -u -t <packagename> command
What I was trying to say was, it would be nice if there was a way to download the build-tools-* package, but the android update command doesnt seem to do partial matches in the -t parameter. So the above is how to determine the correct package name and then update it.
Furthermore, XBMC make apk process doesnt understand this new SDK structure, and it tries to run aapt and dx commands, from the SDK/platform-tools location. But they are actually in SDK/build-tools/19.0.0
So until (if) the make script is updated for the new SDK structure, you have to create symliinks for aapt, dx and libs, in the platform-tools area. The symlink commands are in my post above
Hopefully I explained the issues/workaround for getting XBMC make to work with the newer android SDK structure, in a better way this time?
