New issue
Advanced search Search tips

Issue 907285 link

Starred by 1 user
Status: Available
Owner: ----
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Feature



Sign in to add a comment

Allow to specify adb path when running out/Default/bin scripts

Project Member Reported by bialpio@chromium.org, Nov 21 
Scripts generated as a part of the build & placed in output bin/ directory currently do not allow the user to specify path to adb binary.

The scripts mentioned above leverage apk_operations.py module which does its own adb binary discovery using adb_wrapper & passes it deeper, without an option to explicitly specify path to adb from command line. It might be a good idea to surface path to adb as a command line option.

Comment 1 by agrieve@chromium.org, Dec 21

Components: -Test>Android
Labels: DevX OS-Android
Status: Available (was: Untriaged)
Curious to know more about the use-case here. device_utils.py is not really meant to be compatible with different versions of adb, so might not even work if pointing at another version (although in most cases still should).

Comment 2 by bialpio@chromium.org, Dec 22 

My particular scenario where it was slightly annoying to not be able to specify adb path:
1. Run `adb start-server` on machine A where the android device is connected via USB (this uses default adb installed on the box).
2. Open a tunnel in order to redirect adb server's port (5037) to remote machine  B which has chrome source code & is better suited for building.
3. Attempt to use out/Dirname/bin/ scripts in my case fails due to the fact that the discovered adb comes from chrome repository and doesn't match the version of adb from machine A.

Workaround that worked for me is to create a symlink from adb in chrome repo to the default adb on machine B.

Comment 3 by agrieve@chromium.org, Jan 14

Labels: QuickFix
►

Sign in to add a comment