Package Details: android-sdk-build-tools r35.0.1-1

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.78
First Submitted: 2013-05-16 03:44 (UTC)
Last Updated: 2025-01-24 15:38 (UTC)

Dependencies (6)

Sources (2)

Pinned Comments

aminvakil commented on 2025-03-26 13:43 (UTC)

This repository is maintained at https://github.com/aminvakil/aur.

In case anyone had any suggestions about anything, feel free to raise a PR there.

Latest Comments

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

txtsd commented on 2021-01-03 09:42 (UTC) (edited on 2021-01-04 16:56 (UTC) by txtsd)

Maybe put the binaries/symlinks in /usr/local/bin/

1ace commented on 2021-01-03 08:39 (UTC)

528650baac4e broke the package:

error: failed to commit transaction (conflicting files)
android-sdk-build-tools: /usr/bin/lld exists in filesystem (owned by lld)

txtsd commented on 2020-12-30 14:06 (UTC) (edited on 2020-12-30 14:46 (UTC) by txtsd)

@mynacol Am I manually supposed to source /etc/profile in my zshenv or equivalent? Because the binaries are not in my path.

Nevermind. Reinstalling did the trick. Not sure why it wasn't working before.

mynacol commented on 2020-12-30 14:04 (UTC)

If anyone has warnings regarding the permissions of files, I apologize. The easiest method to fix this is to uninstall and reinstall the latest version of this package.

mynacol commented on 2020-12-30 14:00 (UTC)

@txtsd append_path is a function that /etc/profile provides for scripts in /etc/profile.d/. Any login shell will source /etc/profile, which will source all /etc/profile.d/ scripts. You should do this, else e.g. perl executables under /usr/bin/vendor_perl/ are not in your PATH.

Nonetheless, I did introduce the symlinks, primarily, because in the directory with the executables are other files. Anyone who wants to use other exectables with the same name should prepend the PATH.

txtsd commented on 2020-12-27 13:56 (UTC)

Also why not just make symlinks to the executables in /usr/bin/ since this package is not tied to any version?

txtsd commented on 2020-12-27 12:41 (UTC) (edited on 2020-12-27 12:41 (UTC) by txtsd)

/etc/profile.d/android-sdk-build-tools.sh: line 1: append_path: command not found

What package is this command a part of?

OJFord commented on 2020-12-16 17:12 (UTC)

@mynacol Ah yes, that would be good please - I have a better reason now too, since upgrading meant my (it happened to be a symlink, but, equivalently, PATH) solution broke, due to the directory name change.

I don't think I source from /etc/profile.d/* currently, but it seems like I probably should be, so that's fine, thanks.

mynacol commented on 2020-11-29 17:57 (UTC)

@OJFord Up to now, no one has complained. If you want it, I can set it up. In the PKGBUILD is a relevant section, but commented out.

OJFord commented on 2020-11-29 17:08 (UTC)

Is it intended that aapt et al. end up in /opt/android-sdk/build-tools/30.0.2/; likely not on PATH?

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