<div dir="ltr">Hi all,<br><br><div>However things in SDK Build-tools and SDK Platform-tools are a little bit worse. Their tools come from various repo, and one single repo contains tools belonging to various SDK *-tools. Also note that the mksdcard in SDK Tools is from platform/sdk instead of platform/tool/* .</div><div><br></div><div>By the way, I bought a VPN just now and I can reach you guys finally :)</div><div><br></div><div>Cheers,</div><div>Kai-Chung Yan</div></div><br><div class="gmail_quote"><div dir="ltr">Hans-Christoph Steiner <<a href="mailto:hans@at.or.at">hans@at.or.at</a>> 於 2015年7月9日週四 上午2:21寫道：<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Yeah, platform/tools is the root dir of all this, but there is not<br>
platform/tools git repo, only git repos under that, e.g.:<br>
<br>
<a href="https://android.googlesource.com/platform/tools/base.git" rel="noreferrer" target="_blank">https://android.googlesource.com/platform/tools/base.git</a><br>
<a href="https://android.googlesource.com/platform/tools/buildSrc.git" rel="noreferrer" target="_blank">https://android.googlesource.com/platform/tools/buildSrc.git</a><br>
<a href="https://android.googlesource.com/platform/tools/swt.git" rel="noreferrer" target="_blank">https://android.googlesource.com/platform/tools/swt.git</a><br>
<br>
That's how the `repo` tool sets things up. Its a bit bizarre, but `repo` is<br>
used to build all Android ROMs as well as a lot of the SDK. The<br>
androidsdk-tools source package should be set up to mirror that setup. It<br>
looks like it already is, but it needs some improvements.<br>
<br>
About those build instructions, we'll have to change all `./gradlew` calls to<br>
be just `gradle`, and then find all jar dependencies in Debian. One idea is<br>
to make a patch that removes `mavenCentral()` and `jcenter()` from all<br>
build.gradle files, then add static paths to find the jars using /usr/share/java<br>
<br>
.hc<br>
<br>
Komal Sukhani:<br>
> Hello Hans,<br>
><br>
> From Android Tools Site[1], I have found that platform/tools.git is root<br>
> project and all SDK tools are built under it.<br>
><br>
> [1] <a href="http://tools.android.com/build/gradleplugin" rel="noreferrer" target="_blank">http://tools.android.com/build/gradleplugin</a><br>
><br>
> Komal Sukhani<br>
><br>
> On Tue, Jul 7, 2015 at 12:31 AM, Hans-Christoph Steiner <<a href="mailto:hans@at.or.at" target="_blank">hans@at.or.at</a>><br>
> wrote:<br>
><br>
>><br>
>> I checked out the git repos, since these all seem to be built using<br>
>> gradle, we<br>
>> should try to mimic the official Google setup as much as possible. For a<br>
>> repo<br>
>> like platform/tools/buildSrc.git I think having that as a standalone source<br>
>> package will just create work, since lots of things depend on it, but it<br>
>> doesn't create anything.<br>
>><br>
>> Has anyone found any documentation of how Google builds all this? I<br>
>> imagine<br>
>> it is similar to how Android ROMs are built, using multiple git repos<br>
>> managed<br>
>> using `repo`, and built all together at once.<br>
>><br>
>> .hc<br>
>><br>
>> Hans-Christoph Steiner:<br>
>>><br>
>>> I'm CCing the android-tools list.<br>
>>><br>
>>> I think it makes sense to make a source package per git repo, unless<br>
>> Google is moving around important files between them a lot, like we saw<br>
>> with AndroidConfig.h. All of the android-platform-* source packages are<br>
>> already organized like that. My main concern with this approach is that it<br>
>> might mean a lot of work in the short term.<br>
>>><br>
>>> Yeah, the git release tags are a nightmare, they are not consistent nor<br>
>> documented much. I think for now, we should just go with our best guess as<br>
>> to what is the right tag, then we can adjust in the future.<br>
>>><br>
>>> .hc<br>
>>><br>
>>> On Jul 5, 2015, at 8:39 AM, Komal Sukhani wrote:<br>
>>><br>
>>>> Hello Kai-Chung,<br>
>>>><br>
>>>> Those methods are introduced in higher version of libraries. For<br>
>> example, methods like getAbis(), getDensity() of ddmlib v23.1.0 are used.<br>
>>>><br>
>>>> Komal Sukhani<br>
>>>><br>
>>>> On Sat, Jul 4, 2015 at 2:45 AM, 殷啟聰 <<a href="mailto:seamlikok@gmail.com" target="_blank">seamlikok@gmail.com</a>> wrote:<br>
>>>> Hi Komal,<br>
>>>><br>
>>>> Perhaps those APIs that reported missing are actually in buildSrc?<br>
>>>><br>
>>>> Hi Hans,<br>
>>>><br>
>>>> We found that the android-xxx tags does not exist in all repos, for<br>
>> example platform/tools/buildSrc.<br>
>>>><br>
>>>> Cheers,<br>
>>>> Kai-Chung Yan<br>
>>>><br>
>>>><br>
>>>> 2015 年 7 月 4 日 (週六)04:51 <Komal Sukhani> 於 <a href="mailto:komaldsukhani@gmail.com" target="_blank">komaldsukhani@gmail.com</a> 寫道：<br>
>>>> Hello,<br>
>>>><br>
>>>> I hope you are enjoying in California.<br>
>>>><br>
>>>> This week I have been working on Android plugin for Gradle. The plugin<br>
>> has dependency over some<br>
>>>> of Java libraries like sdklib, ddmlib etc. These libraries are provided<br>
>> by source package androidsdk-tools<br>
>>>> but their current version is 22.2 and one used by plugin is 24.2.0. I<br>
>> have tried using existing libraries but<br>
>>>> Gradle plugin refers to some of methods that were introduced in higher<br>
>> version. So update is must.<br>
>>>><br>
>>>> androidsdk-tools package is fetching code from two different repo,<br>
>>>> - tools/base<br>
>>>> - tools/swt<br>
>>>><br>
>>>> Kai-Chung and I were thinking instead of updating the package, it would<br>
>> be easier to maintain the package<br>
>>>> if we create two separate packages for repos tools/base and tools/swt<br>
>> namely android-platform-tools-base<br>
>>>> and android-platform-tools-build. This will cover all SDK tools and<br>
>> Android-Gradle-Plugin, but there will<br>
>>>> be two source packages for SDK tools.<br>
>>>><br>
>>>> What do you suggest?<br>
>>>><br>
>>>> Komal Sukhani<br>
>>>> --<br>
>>>> 殷啟聰 | Kai-Chung Yan<br>
>>>> 一生只向真理與妻子低頭<br>
>>>> Full-time student of Providence University of Taiwan<br>
>>>> LinkedIn: <<a href="https://linkedin.com/in/seamlik" rel="noreferrer" target="_blank">https://linkedin.com/in/seamlik</a>><br>
>>>> Blog: <<a href="http://seamlik.logdown.com" rel="noreferrer" target="_blank">seamlik.logdown.com</a>><br>
>>>><br>
>>>><br>
>>><br>
>>><br>
>><br>
>> _______________________________________________<br>
>> Android-tools-devel mailing list<br>
>> <a href="mailto:Android-tools-devel@lists.alioth.debian.org" target="_blank">Android-tools-devel@lists.alioth.debian.org</a><br>
>> <a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel" rel="noreferrer" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel</a><br>
><br>
</blockquote></div><div dir="ltr">-- <br></div><div dir="ltr"><p dir="ltr">殷啟聰 | Kai-Chung Yan<br>
一生只向真理與妻子低頭<br>
Full-time student of Providence University of Taiwan<br>
LinkedIn: <<a href="https://linkedin.com/in/seamlik">https://linkedin.com/in/seamlik</a>><br>
Blog: <<a href="http://seamlik.logdown.com">seamlik.logdown.com</a>></p>
</div>