Package Details: android-sdk-build-tools r27.0.3-1

Git Clone URL: (read-only)
Package Base: android-sdk-build-tools
Description: Build-Tools for Google Android SDK (aapt, aidl, dexdump, dx, llvm-rs-cc)
Upstream URL:
Licenses: custom
Submitter: xgdgsc
Maintainer: xgdgsc (somekool)
Last Packager: xgdgsc
Votes: 449
Popularity: 2.054699
First Submitted: 2013-05-16 03:44
Last Updated: 2017-12-31 08:23

Latest Comments

somekool commented on 2017-08-19 16:32

@xgdgsc If I get this thing to work locally, you can give me write access if you are still looking for a co-maintainer

somekool commented on 2017-08-19 16:30

please remove lib32-* from the dependencies

farwayer commented on 2017-08-01 00:53

Look like lib32-gcc-libs can be removed and ncurses5-compat-libs, java-environment, bash should be added for x86_64.

xgdgsc commented on 2017-06-22 02:44

android-sdk-build-tools E: Dependency lib32-zlib detected and not included (libraries ['usr/lib32/'] needed in files ['opt/android-sdk/build-tools/26.0.0/mipsel-linux-android-ld', 'opt/android-sdk/build-tools/26.0.0/i686-linux-android-ld', 'opt/android-sdk/build-tools/26.0.0/aarch64-linux-android-ld', 'opt/android-sdk/build-tools/26.0.0/arm-linux-androideabi-ld'])
android-sdk-build-tools E: Dependency clang detected and not included (libraries ['usr/lib/'] needed in files ['opt/android-sdk/build-tools/26.0.0/llvm-rs-cc'])
android-sdk-build-tools W: Dependency included and not needed ('ncurses5-compat-libs')

This is namcap output.

lonaowna commented on 2017-06-21 14:50

@dreamingincode, I tested all the binaries in /opt/android-sdk/build-tools/26.0.0, and all of them seem to work fine. All that link to libz link to the 64-bit one. (check with ldd *)

While testing I also found that /opt/android-sdk/build-tools/26.0.0/bcc_compat doesn't work without the ncurses5-compat-libs package. So that should probably be added as a dependency.

dreamingincode commented on 2017-06-21 14:39

[Removed for being incorrect]

lonaowna commented on 2017-06-21 14:35

The lib32* dependencies are no longer needed. You can just replace depends_i686 and depends_x86_64 with:

depends=('gcc-libs' 'zlib')

('gcc-libs' isn't strictly needed either, since it is part of the base group)

dreamingincode commented on 2017-04-27 02:05

25.0.3 is out:

xgdgsc commented on 2016-11-29 01:59

Anyone interested in becoming co-maintainers?

einbisschen commented on 2016-09-28 06:38

I needed to create the file "/etc/profile.d/" with the content
"export PATH=$PATH:/opt/android-sdk/build-tools/24.0.2"
to make the commands work.

xgdgsc commented on 2016-09-26 13:17

@TamasBarta Why flag? I didn' t find a new version here .

berb commented on 2016-08-24 21:03

Seems like the SHA1 checksum is wrong in the PKGBUILD. The correct one seems to be 84f18c392919a074fcbb9b1d967984e6b2fef8b4 at the moment (as reported in

normalraw commented on 2016-08-24 13:46

There exists a version mismatch wherein the package is installed to `/opt/android-sdk/build-tools/24.0.0` as parsed from `` even though version 24.0.1 has been specified in the PKGBUILD.

As a result, uncommenting the lines responsible for setting $PATH do not work.


xgdgsc commented on 2016-08-13 01:58

@kazik117 I don' t have access to an arch machine now. Would you mind me adding you to co-maintainers to change this?

kazik117 commented on 2016-08-12 20:27

There is a bug version string in file.
I added sed -i "s@24\.0\.0@24\.0\.1@g" "${srcdir}/$_android/" before copying files to destination.

xgdgsc commented on 2016-08-01 02:00

Looking for co-maintainers.

xgdgsc commented on 2016-07-06 01:49

Thanks. Changed.

sjakub commented on 2016-07-05 20:01

I am getting this warning while building with gradle:
Observed package id 'build-tools;24.0.0' in inconsistent location '/opt/android-sdk/build-tools/24' (Expected '/opt/android-sdk/build-tools/24.0.0')

It might be a good idea to use standard paths...

xgdgsc commented on 2016-04-04 01:08

Thsnks. Changed.

edh commented on 2016-04-03 09:08

Please use depends_i686 and depends_x86_64 [1] instead of checking the CARCH.


xgdgsc commented on 2015-09-20 12:16

There' s a package for that: May need to change a few lines as I commented there.

zman0900 commented on 2015-09-20 10:27

Some of the libs included in this are still linked to ncurses 5. Not sure if there is anything that can even be done about it since they come pre-built, but it's probably going to cause problems.

└──╼ for f in $(find /opt/android-sdk/build-tools -type f -executable); do unset OUT; OUT=$(ldd $f | grep 'ncurses.*\.so\.5'); if [ -n "$OUT" ]; then echo "====> $f"; echo -e $OUT; echo ""; fi; done
====> /opt/android-sdk/build-tools/23.0.1/lib/ => not found => not found

====> /opt/android-sdk/build-tools/23.0.1/lib/ => not found

====> /opt/android-sdk/build-tools/23.0.1/lib/ => not found => not found => not found

====> /opt/android-sdk/build-tools/23.0.1/lib/ => not found => not found

====> /opt/android-sdk/build-tools/23.0.1/llvm-rs-cc => not found => not found => not found

====> /opt/android-sdk/build-tools/23.0.1/bcc_compat => not found => not found => not found => not found

tech4david commented on 2015-09-19 10:00

sorry, thought there was a v24 (as android-sdk is v24) so I flagged, can't seem to unflag now.

lybin commented on 2015-05-28 21:24


<sdk:checksum type="sha1">83918bb640a06fb2425af07390e741a4f2ff79ed</sdk:checksum>

xgdgsc commented on 2015-05-07 02:30

@Jesin Why flag out of date? There is no new version.

incomingstick commented on 2015-05-05 16:12

yaourt output when updating:
aur/android-sdk-build-tools r19.0.3-1 -> r22.0.1-1

ishitatsuyuki commented on 2015-03-26 23:51

Please add DYNAMIC DEPENDENCIES. This will refuse to build on i686 platform.

lcartercondon commented on 2014-11-02 05:41


lcartercondon commented on 2014-11-02 05:40

egore911 commented on 2014-11-01 18:27

21.1 was released

felixonmars commented on 2014-10-24 15:45

Looks like a typo in PKGBUILD: _ver=21.02. => _ver=21.0.2

mvdan commented on 2014-07-17 07:06

No idea, sorry. But I suppose sed isn't that bad.

Teasp00n commented on 2014-07-09 01:50

@mvdan: Yeah that should work. I tried that at some point but it didn't work. It's more likely that I botched it though. Is there any way to do that in the pkgbuild that doesn't require some epic sed-fu or something?

mvdan commented on 2014-06-30 15:43

@Teasp00n: What about placing them in the right order, so that the clang package binary takes precedence over the one in this package? I think that we should place the clang path before this one in order for that to work. I suppose we can play with the names of the scripts to make the other one come before this one. This would not normally happen since 'android-' comes before 'clang', I guess.

Also, the right package version is 20.0.0. If you want to use the number 20 that's fine, but the install path should still be 20.0.0 as in /opt/android-sdk/build-tools/20.0.0. Changing it is just asking for trouble :)

Teasp00n commented on 2014-06-29 08:29

@mvdan: Sorry for the extremely late reply. I didn't see your comment. The problem is `which clang` returns the one in the android tools directory and not the version of clang explicitly installed on the system. I've had local builds fail because of this. Something about the symbols of libraries not being compatible/ valid. If I remove the android build tools from the path the problem is solved. That said, I also use the tools on the command line. I would prefer that they were still on the path, it's only the bundled clang I have an issue with.

Anonymous comment on 2014-06-26 20:30

Upgraded PKGBUILD for r20 and switch to https

klusark commented on 2014-06-26 18:00

Version 20 is out

mvdan commented on 2014-05-22 15:10

For what it's worth, I do use the build-tools from the command line, and not having PATH set up automatically is a tad sub-optimal. What problems does Clang have with this, exactly? Are there some binaries that conflict?

xgdgsc commented on 2014-04-18 06:15

Well, if it conflicts, I think removing the adding to PATH should be fine. Most people just use IDEs that can find these things. Is removing it OK for most of you?

Teasp00n commented on 2014-04-18 05:55

/etc/profile.d/ is adding the build-tools to the PATH (I would hazard a guess deliberately ;) ). This does however cause issues when attempting to link with libclang. Are there are accepted solutions to this currently? I can override the PATH for the terminal session I'm using as a workaround but I would prefer something a little more seamless. Thoughts?

jumperpunk commented on 2014-02-28 15:11

I'm getting a trailing '/' on the path for this. I glanced at the PKGBUILD and didn't see why. Not a huge deal as it still works, but I thought you may want to look into it.

B_Lizzard commented on 2014-01-31 15:28

Not outdated, I accidentally clicked while trying to download it. :)

giniu commented on 2013-10-16 13:48

According to android sdk manager, there is already 18.1.1

Anonymous comment on 2013-09-11 13:38

Sorry, it's not outdated. I clicked accidentally when trying to vote for it.

arielp commented on 2013-08-05 20:49

Possibly add options=('!strip')

xgdgsc commented on 2013-05-16 12:37

Google splitted platform-tools.