system adb conflicts with hunter adb

[headupinclouds]

TODO: Either provide an easy way to export the hunter provided adb for development use, or provide an option to use the system adb while in development mode. Probably the first option is more compatible with hunter goals, but both could work well in practice.

This turns up in the scenario with Hunter is running adb commands for testing or launching applications, and a user runs a system adb logcat or adb shell for debugging.

[ruslo]

This turns up in the scenario with Hunter is running adb commands for testing or launching applications, and a user runs a system adb logcat or adb shell for debugging

Is there any problem with it?

Either provide an easy way to export the hunter provided adb for development use

On *nix we can create symlink to the adb in CMAKE_BINARY_DIR (i.e. on _builds/<toolchain>). On Windows it can be *.bat file which will update PATH, or adb.bat which will run real adb from Hunter.

[headupinclouds]

Is there any problem with it?

This was a note for an issue I ran into, and isn't very high priority. The main issue is that it leads to an adb server/client version mismatch. I get adb server version (32) doesn't match this client (36); killing... In my latest test, adb seems to take care of this itself. I previously ran into a situation where it seemed I had to kill adb manually. If this doesn't turn up again in testing I'll close it.

[headupinclouds]

I recall the core issue. If you are running something like make facefilter-launch which is managed by the hunter adb, and you want to observe the logs while the program is running via the (system) adb logcat...

[ruslo]

If this doesn't turn up again in testing I'll close it

No, it's a valid issue that need to be solved. I was just wondering about any real erros.