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: 483
Popularity: 1.10
First Submitted: 2013-05-16 03:44 (UTC)
Last Updated: 2024-06-17 17:52 (UTC)

Dependencies (6)

Sources (2)

Latest Comments

1 2 3 4 5 6 .. 11 Next › Last »

aminvakil commented on 2024-06-17 17:57 (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.

mynacol commented on 2024-06-15 17:47 (UTC)

As I reduce my usage of Arch, I drop the maintainership of this package. I hope someone invested will continue it.

mynacol commented on 2024-05-05 20:20 (UTC)

@dreieck I won't add conflicts/provides for other AUR packages. But I've seen you found another solution already :)

dreieck commented on 2024-05-05 11:59 (UTC)

Please add zipalign to the conflicts array (conflicting file is /usr/bin/zipalign):

llamafile-bin: /usr/bin/zipalign exists in filesystem (owned by android-sdk-build-tools)

And maybe also add it to the provides array.

Regards and thanks for maintaining!

mynacol commented on 2022-12-04 20:13 (UTC)

Thanks @NextAlone for the comment. I opted to create explicit variables for major, minor and micro version numbers instead of your suggestion 👍

NextAlone commented on 2022-12-03 16:38 (UTC) (edited on 2022-12-03 16:42 (UTC) by NextAlone)

Something wrong with dest dir, r33.0.1 installed into /opt/android-sdk/build-tools/33.0.1.0.0, and version is detected as 0.0.0, so changes are below, may this be reviewed and fixed.

diff --git a/PKGBUILD b/PKGBUILD
index 5a32dda..7576c65 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -26,12 +26,12 @@ package() {
   cd "$pkgdir"

   install -d usr/share/licenses/$pkgname/
-  ln -s /opt/$_sdk/build-tools/$_ver.0.0/NOTICE.txt usr/share/licenses/$pkgname/NOTICE.txt
-  sed -i "s/@major@/$_ver/g;s/@minor@/0/g;s/@micro@/0/g" "$srcdir/package.xml"
-  install -Dm644 "${srcdir}/package.xml" opt/$_sdk/build-tools/$_ver.0.0/package.xml
-  ln -s /opt/$_sdk/build-tools/$_ver.0.0/package.xml usr/share/licenses/$pkgname/package.xml
+  ln -s /opt/$_sdk/build-tools/$_ver/NOTICE.txt usr/share/licenses/$pkgname/NOTICE.txt
+  sed -i "s/@major@/${_ver:0:0-4}/g;s/@minor@/${_ver:0-3:1}/g;s/@micro@/${_ver:0-1:1}/g" "$srcdir/package.xml"
+  install -Dm644 "${srcdir}/package.xml" opt/$_sdk/build-tools/$_ver/package.xml
+  ln -s /opt/$_sdk/build-tools/$_ver/package.xml usr/share/licenses/$pkgname/package.xml

-  target="opt/$_sdk/build-tools/$_ver.0.0"
+  target="opt/$_sdk/build-tools/$_ver"
   mkdir -p "$target"
   cp -r "$srcdir/$_android/"* "$target"
   chmod +Xr -R "$target"

Floriantoine commented on 2022-08-09 12:01 (UTC)

I use Quasar with cordova which allows to put an application on mobile, cordova uses android-sdk-build-tools, when I launch the build it gives me a message that I had not signed the packages! but i finally found the problem. the command line signs in the wrong place! you had to move the signatures for cordova to detect them!

Sorry for not updating my post! I hope this can help someone else!

mynacol commented on 2022-08-09 11:17 (UTC)

@Floriantoine: Can you provide more information/error messages?

I don't sign AUR packages, but I can't imagine a reason why this particular package would have problems being signed. Maybe check with the documentation how to sign packages again?

Floriantoine commented on 2022-08-03 13:53 (UTC)

Is still impossible for me to sign the package, I place the order the return tells me that everything is well signed, yet nothing concerning this package... a solution ?

mynacol commented on 2022-07-15 16:57 (UTC)

Hi @gnaggnoyil, android-sdk-build-tools does contain d8 and some other executables. They are stored in a directory with non-executables, so adding it to the PATH is problematic. Thus I created the symlinks.

I made an exception for lld, which is a package in the official repos. I do not intend to add another exception for an AUR package. The question is: what happens when you manually remove the symlink or install v8-r with pacman -U --overwrite /usr/bin/d8 [pkg]?