Package Details: android-sdk-build-tools r34.0.0-2

Git Clone URL: https://aur.archlinux.org/android-sdk-build-tools.git (read-only, click to copy)
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
Keywords: android
Licenses: custom
Submitter: xgdgsc
Maintainer: aminvakil
Last Packager: aminvakil
Votes: 484
Popularity: 0.185813
First Submitted: 2013-05-16 03:44 (UTC)
Last Updated: 2024-06-17 17:52 (UTC)

Dependencies (6)

Sources (2)

Latest Comments

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 Next › Last »

tsp commented on 2014-07-09 01:50 (UTC)

@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 (UTC)

@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 :)

tsp commented on 2014-06-29 08:29 (UTC)

@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.

<deleted-account> commented on 2014-06-26 20:30 (UTC)

Upgraded PKGBUILD for r20 and switch to https http://pastebin.com/raw.php?i=iLr1VPEX

klusark commented on 2014-06-26 18:00 (UTC)

Version 20 is out http://dl-ssl.google.com/android/repository/build-tools_r20-linux.zip

mvdan commented on 2014-05-22 15:10 (UTC)

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 (UTC)

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?

tsp commented on 2014-04-18 05:55 (UTC)

/etc/profile.d/android-sdk-build-tools.sh 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?

a172 commented on 2014-02-28 15:11 (UTC)

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 (UTC)

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

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 Next › Last »