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

Git Clone URL: https://aur.archlinux.org/android-sdk-build-tools.git (read-only)
Package Base: android-sdk-build-tools
Description: Build-Tools for Google Android SDK (aapt, aidl, dexdump, dx, llvm-rs-cc)
Upstream URL: https://developer.android.com/studio/releases/build-tools
Licenses: custom
Submitter: xgdgsc
Maintainer: xgdgsc (somekool)
Last Packager: xgdgsc
Votes: 456
Popularity: 0.703014
First Submitted: 2013-05-16 03:44
Last Updated: 2018-10-01 01:39

Latest Comments

1 2 3 4 5 6 Next › Last »

kyak commented on 2019-05-19 09:45

Please remove the lib32-* dependencies or mark them as optional.

I have to enable the multilib repository just for lib32-zlib dependency of android-sdk-build-tools.

rpodgorny commented on 2018-09-18 23:12

just a cosmetic note -> the PKGBUILD has the executable flag...

xgdgsc commented on 2018-09-18 01:10

Adding to PATH used to cause problems https://aur.archlinux.org/packages/android-sdk-build-tools/?O=40&PP=10 . I don 't know if it still does now. You' d better create yourself for now.

fordprefect commented on 2018-09-17 11:43

could you add a link to the apksigner binary to /usr/bin so it appears in the PATH?

mattsturgeon commented on 2018-05-13 14:10

As hinted at earlier by @einbisschen, this package should create /etc/profile.d/android-sdk-build-tools.sh with the content export PATH=$PATH:/opt/android-sdk/build-tools/27.0.3

Perhaps adding mkdir -p etc/profile.d and echo -e "export PATH=\"\$PATH:/opt/$_sdk/build-tools/$ver\"\n" > $pkgdir/etc/profile.d/$pkgname.sh to PKGBUILD would do the trick?

EDIT: it may also make sense to have a latest symlink... Something like ln -sf /opt/$_sdk/build-tools/$ver opt/$_sdk/build-tools/latest, if so perhaps this should be what is added to the PATH instead. Although it is probably a good idea to check no higher version already exists, which may make a simple feature a bit more complex.

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/libz.so.1'] 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/libclang.so'] 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.