Android Debug Bridge (adb) is a versatile command line tool that
lets you communicate with an emulator instance or connected
Android-powered device.
WWW: http://developer.android.com/tools/help/adb.html
===> The following configuration options are available for android-tools-adb-29.0.6_1:
BASH=off: Install programmable completions for Bash
DOCS=on: Build and/or install documentation
MDNSRESPONDER=on: Zeroconf support via mDNSResponder
TEST=off: Build and/or run tests
TEST_PYTHON=off: Build and/or run python tests
===> Use 'make config' to modify these settings
devel/android-tools: New port: Android debugging tools
While I'm here, remove the old devel/android-tools-adb and
devel/android-tools-fastboot ports. These ports are long out-of-date
and the adb port especially had issues with certain devices.
This port was tested from a FreeBSD 14.0 system to flash both
LineageOS and GrapheneOS on a Google Pixel 3 using both `adb` and
`fastboot`.
*/*: Remove redundant '-*' from CONFLICTS definitions
The conflict checks compare the patterns first against the package
names without version (as reported by "pkg query "%n"), then - if
there was no match - agsinst the full package names including the
version (as reported by "pkg query "%n-%v").
Approved by: portmgr (blanket)
Fix build with src r354909 applied.
The referenced change made NO_INSTALLLIB, NO_MAN, and NO_PROFILE into
errors causing these ports that declare them and use the FreeBSD make
infrastructure as part of their build to fail.
When the offending variables occur in a BSD Makefile, NO_MAN becomes
MAN= and NO_INSTALLLIB and NO_PROFILE become MK_INSTALLLIB=no and
MK_PROFILE=no respectively. When declared in the environment they
become WITHOUT_<FOO>.
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
devel/android-tools-adb: switch to LIBUSB_CAP_HAS_HOTPLUG whitelist
$ adb connect 1.2.3.4
* daemon not running; starting now at tcp:5037
ADB server didn't ACK
Full server startup log: /tmp/adb.1000.log
Server had pid: 1193
--- adb starting (pid 1193) ---
adb I 12-31 10:41:58 1193 1 main.cpp:56] Android Debug Bridge version
1.0.40
adb I 12-31 10:41:58 1193 1 main.cpp:56] Version 28.0.0-0
adb I 12-31 10:41:58 1193 1 main.cpp:56] Installed as /usr/pkg/bin/adb
adb I 12-31 10:41:58 1193 1 main.cpp:56]
adb F 12-31 10:41:58 1193 1 usb_libusb.cpp:517] failed to register libusb
hotplug callback
* failed to start daemon
error: cannot connect to daemon
Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
devel/android-tools-adb: unbreak on DragonFly after r477244
adb/client/usb_libusb.cpp: In function 'void libusb::poll_for_devices()':
adb/client/usb_libusb.cpp:493:43: error: unable to find numeric literal operator
'operator""ms'
if (device_poll_cv.wait_for(lock, 500ms, []() { return
terminate_device_poll_thread; })) {
^~~~~
devel/android-tools-adb: update SDK version as part of makesum
- Extract platform SDK version out of platform/build repo
- Move version logic out of sub-makefile
- Simplify GH_REVISION
devel/android-tools-{adb,fastboot}: chase SDK version in --version after r456869
Keep in mind, the output is still not identical to upstream.
$ platform-tools_r26.0.0-linux/adb version
Android Debug Bridge version 1.0.39
Revision 3db08f2c6889-android
Installed as /tmp/platform-tools_r26.0.0-linux/adb
$ platform-tools_r26.0.0-linux/fastboot --version
fastboot version 3db08f2c6889-android
Installed as /tmp/platform-tools_r26.0.0-linux/fastboot
$ platform-tools_r27.0.0-linux/adb version
Android Debug Bridge version 1.0.39
(Only the first 15 lines of the commit message are shown above )
Convert Python ports to FLAVORS.
Ports using USE_PYTHON=distutils are now flavored. They will
automatically get flavors (py27, py34, py35, py36) depending on what
versions they support.
There is also a USE_PYTHON=flavors for ports that do not use distutils
but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if
using distutils but flavors are not wanted.
A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
added to cope with Python ports that did not have the Python
PKGNAMEPREFIX but are flavored.
USES=python now also exports a PY_FLAVOR variable that contains the
(Only the first 15 lines of the commit message are shown above )
Bump PORTREVISION for ports depending on the canonical version of GCC
(via Mk/bsd.default-versions.mk and lang/gcc) which has moved from
GCC 5.4 to GCC 6.4 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++11-lang,
c++14-lang, c++0x, c11, or gcc-c++11-lib.
PR: 219275
Bump PORTREVISIONs for ports depending on the canonical version of GCC and
lang/gcc which have moved from GCC 4.9.4 to GCC 5.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using using Mk/bsd.octave.mk which in turn has USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++14-lang,
c++11-lang, c++0x, c11, or gcc-c++11-lib.
PR: 216707
Drop pre-10.3 support in my ports
Figuring out which GCC hacks are safe to drop is tricky but at least
devel/fb-adb is limited to x86 due to ADA bootstrap.
devel/android-tools-adb: unbreak build on DragonFly
make(1) suffix rules discard original extension as used by bsd.*.mk
which leads to unpredictable behavior if more than one candidate is
found under ${.PATH}. So, partially qualify pathname to avoid
accidentally building libcutils/sockets.c despite SRCS=sockets.cpp
$ echo 'void foo() { }' > a.c
$ echo 'int main() { }' > a.cxx
$ make PROG_CXX=test SRCS=a.cxx NO_MAN= -f /usr/share/mk/bsd.prog.mk
cc -O -pipe -std=gnu99 -c a.c
c++ -O -pipe -o test a.o
/usr/lib/crt1.o: In function `_start':
crt1.c:(.text+0x132): undefined reference to `main'
*** Error code 1
(Only the first 15 lines of the commit message are shown above )
devel/android-tools-{adb,fastboot}: force all distfiles for |make makesum|
Forgetting to pass DISABLE_CONFLICTS= is easy to notice unlike
a missing checksum. So, hook into makesum like with update-revision.
devel/android-tools-{adb,fastboot}: update BASH to 20150902 snapshot
- Switch to the actual upstream on GitHub
- Reduce overuse of :FOO make(1) variable modifiers
- Restore conditional install via target option helper
devel/android-tools-*: slightly improve standalone build
- Try to derive {ADB,FASTBOOT}_REVISION from git(1)
- Use pkg-config for libcrypto/libpcre/libusb (e.g. if they aren't in base)
- Convert PORTDOCS into FILES (bsd.port.mk vs. bsd.prog.mk)
- Partially convert to new testing framework
- Put -lpthread last as enforced by base r274849 but prevent
:= assignment from mucking $ escaping in $()
- |make clean| to clean files built by test target
- Move up bsd.prog.mk in order to use ${PROG} and ${OBJS} defined in it
devel/android-tools-adb: unbreak TEST=on more reliably
/dev/full is only provided by default on 11.0, earlier releases have it
in lindev(4). This leads to the same error as with automation. Other BSDs
including DragonFly don't provide /dev/full at all.
[ RUN ] io.WriteFdExactly_ENOSPC
adb_io_test.cpp:136: Failure
Expected: (-1) != (fd), actual: -1 vs -1
[ FAILED ] io.WriteFdExactly_ENOSPC (1 ms)
Reported by: Barbara <barbara.freebsd@gmail.com>
devel/android-tools-adb: add missing USE_OPENSSL for -lcrypto
Bump PORTREVISION for those who build everything against
security/openssl or security/libressl.
devel/android-tools-adb-devel: add new slave port for git master
A temporary port to facilitate testing and updating master.
While copying usb_libusb.c [1] under FILESDIR clean it up:
- Add static keyword for file-local functions
- Fix const usage exposed in C++ mode [2]
- Fix casting 3rd argument of libusb_bulk_transfer(3) exposed in C++ mode
- Fix inconsistent whitespace: trailing, tabs + spaces, bogus indentation
- Fix typo in usb_kick() trace message
- Fix fprintf(3) warning in scan_usb_devices() trace message
- Convert err(3) usage to fatal_errno()
- Drop BSDism of sysexits(3)
- Drop unecessary struct keyword
- Drop unused headers [2]
(Only the first 15 lines of the commit message are shown above )
devel/android-tools-adb: fix "get-devpath" output
Catch up with the following upstream change:
https://android.googlesource.com/platform/system/core/+/e109d26%5E!/
Before
$ adb get-devpath
unknown
$ adb devices -l
List of devices attached
ABCD1234 device product:A1 model:Blah device:foo
(Only the first 15 lines of the commit message are shown above )
devel/android-tools-adb: convert to BSD-style Makefile
- Supports building with multiple jobs
- No longer depends on devel/gmake
Differential Revision: https://reviews.freebsd.org/D2862
Obtained from: devel/android-tools-fastboot (based on)
Approved by: kevlo (maintainer)
Import Android adb tool.
Android Debug Bridge (adb) is a versatile command line tool that
lets you communicate with an emulator instance or connected
Android-powered device.
