Arch Linux User Repository

@xyproto that's a good idea, please adopt

Hi nvllsvm, would you mind if I adopted and moved this useful tool to [community]?

@al3xxx: I can't reproduce that using the arch-meson wrapper.

Hi, Couldn't build it without PKG file modification (meson configure requires explicit mentioning of libcrypto for linking otherwise linker spits out long list of errors like these /usr/bin/ld: /usr/lib/libssh.so.4: undefined reference to DSA_free@OPENSSL_1_1_0' /usr/bin/ld: /usr/lib/libssh.so.4: undefined reference toBN_copy@OPENSSL_1_1_0' /usr/bin/ld: /usr/lib/libssh.so.4: undefined reference to `EVP_PKEY_get1_EC_KEY@OPENSSL_1_1_0' )

Here is proper meson configuration command

 meson \
 --prefix /usr \
 --buildtype release \
 --strip \
 -Db_lto=true \
 -Dc_link_args=-lcrypto \                                             
 #^^^^^^^^^^^^^^^^^^^^^
 -Dprebuilt_server="../scrcpy-server-v${pkgver}" \

@nvllsvm Recently, starting scrcpy via terminal shows:

INFO: scrcpy 1.12.1 https://github.com/Genymobile/scrcpy /usr/share/scrcpy/scrcpy-server: 1 file pushed, 0 skipped. 2.0 MB/s (26202 bytes in 0.013s) INFO: Initial texture: 1440x2880

It then opens a new terminal window, but does not mirror the smartphone screen. Any ideas for a fix? Thanks in advance.

Small question. Can the sourcelink for scrcpy be prepended with ${pkgname}-${pkgver}.tar.gz::? Makes life easier for people which set SRCDEST in makepkg.conf

@Gilrain I actually made some dummy package for Flutter SDK long time ago but not for Android SDK and tools. Maybe I will make one for android-tools and android-sdk later. Thank you for the tip.

@rockypra Why don't you use package relations [https://wiki.archlinux.org/index.php/PKGBUILD#Package_relations] when building your custom ADB?

I think android-tools should be an optional and removed from mandatory deps list. Someone who want to use this package should know that it requires ADB and there is a lot of way of making ADB and any other tools provided by android-tools available to the system. Having android-tools installed alongside the self-managed one is just adding more unneeded redundancy and sometimes conflicts if the self-managed tools are newer than tools provided by Arch Linux package.

I personally had some issue with android-tools package before which is I'm not sure if it's fixed or not, so I started to manage Android development stuff by myself and I prefer to do it that way rather than waiting for Arch Linux team to update their packages.

@nvllsvm The rm -rf build in the prepare() function is unnecessary. If you want to clean up leftovers from previous builds just add -c/--clean to your makepkg command (see: https://wiki.archlinux.org/index.php/Makepkg#Usage).