[Android-tools-devel] Updating SDK tools

[Hans-Christoph Steiner]

Yeah, platform/tools is the root dir of all this, but there is not
platform/tools git repo, only git repos under that, e.g.:

https://android.googlesource.com/platform/tools/base.git
https://android.googlesource.com/platform/tools/buildSrc.git
https://android.googlesource.com/platform/tools/swt.git

That's how the `repo` tool sets things up.  Its a bit bizarre, but `repo` is
used to build all Android ROMs as well as a lot of the SDK.  The
androidsdk-tools source package should be set up to mirror that setup. It
looks like it already is, but it needs some improvements.

About those build instructions, we'll have to change all `./gradlew` calls to
be just `gradle`, and then find all jar dependencies in Debian.  One idea is
to make a patch that removes `mavenCentral()` and `jcenter()` from all
build.gradle files, then add static paths to find the jars using /usr/share/java

.hc

Komal Sukhani:
> Hello Hans,
> 
> From Android Tools Site[1], I have found that platform/tools.git is root
> project and all SDK tools are built under it.
> 
> [1] http://tools.android.com/build/gradleplugin
> 
> Komal Sukhani
> 
> On Tue, Jul 7, 2015 at 12:31 AM, Hans-Christoph Steiner <hans at at.or.at>
> wrote:
> 
>>
>> I checked out the git repos, since these all seem to be built using
>> gradle, we
>> should try to mimic the official Google setup as much as possible.  For a
>> repo
>> like platform/tools/buildSrc.git I think having that as a standalone source
>> package will just create work, since lots of things depend on it, but it
>> doesn't create anything.
>>
>> Has anyone found any documentation of how Google builds all this?  I
>> imagine
>> it is similar to how Android ROMs are built, using multiple git repos
>> managed
>> using `repo`, and built all together at once.
>>
>> .hc
>>
>> Hans-Christoph Steiner:
>>>
>>> I'm CCing the android-tools list.
>>>
>>> I think it makes sense to make a source package per git repo, unless
>> Google is moving around important files between them a lot, like we saw
>> with AndroidConfig.h.  All of the android-platform-* source packages are
>> already organized like that. My main concern with this approach is that it
>> might mean a lot of work in the short term.
>>>
>>> Yeah, the git release tags are a nightmare, they are not consistent nor
>> documented much.  I think for now, we should just go with our best guess as
>> to what is the right tag, then we can adjust in the future.
>>>
>>> .hc
>>>
>>> On Jul 5, 2015, at 8:39 AM, Komal Sukhani wrote:
>>>
>>>> Hello Kai-Chung,
>>>>
>>>> Those methods are introduced in higher version of libraries. For
>> example, methods like getAbis(), getDensity() of ddmlib v23.1.0 are used.
>>>>
>>>> Komal Sukhani
>>>>
>>>> On Sat, Jul 4, 2015 at 2:45 AM, 殷啟聰 <seamlikok at gmail.com> wrote:
>>>> Hi Komal,
>>>>
>>>> Perhaps those APIs that reported missing are actually in buildSrc?
>>>>
>>>> Hi Hans,
>>>>
>>>> We found that the android-xxx tags does not exist in all repos, for
>> example platform/tools/buildSrc.
>>>>
>>>> Cheers,
>>>> Kai-Chung Yan
>>>>
>>>>
>>>> 2015 年 7 月 4 日 (週六)04:51 <Komal Sukhani> 於 komaldsukhani at gmail.com 寫道：
>>>> Hello,
>>>>
>>>> I hope you are enjoying in California.
>>>>
>>>> This week I have been working on Android plugin for Gradle. The plugin
>> has dependency over some
>>>> of Java libraries like sdklib, ddmlib etc. These libraries are provided
>> by source package androidsdk-tools
>>>> but their current version is 22.2 and one used by plugin is 24.2.0. I
>> have tried using existing libraries but
>>>> Gradle plugin refers to some of methods that were introduced in higher
>> version. So update is must.
>>>>
>>>> androidsdk-tools package is fetching code from two different repo,
>>>>                              - tools/base
>>>>                              - tools/swt
>>>>
>>>> Kai-Chung and I were thinking instead of updating the package, it would
>> be easier to maintain the package
>>>> if we create two separate packages for repos tools/base and tools/swt
>> namely android-platform-tools-base
>>>> and android-platform-tools-build. This will cover all  SDK tools and
>> Android-Gradle-Plugin, but there will
>>>> be two source packages for SDK tools.
>>>>
>>>> What do you suggest?
>>>>
>>>> Komal Sukhani
>>>> --
>>>> 殷啟聰 | Kai-Chung Yan
>>>> 一生只向真理與妻子低頭
>>>> Full-time student of Providence University of Taiwan
>>>> LinkedIn: <https://linkedin.com/in/seamlik>
>>>> Blog: <seamlik.logdown.com>
>>>>
>>>>
>>>
>>>
>>
>> _______________________________________________
>> Android-tools-devel mailing list
>> Android-tools-devel at lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel
>