Summary

Create a method to detect a test binary already on the target ; Owner: Tim ; Reporter: AGL, Tim, Siemens ; Status: in-progress ; Priority: medium

; Summary: Create a method to detect a test binary already on the target
; Owner: Tim
; Reporter: AGL, Tim, Siemens
; Status: in-progress
; Priority: medium

Description [edit section]

= Description =
Create a method to search for a test binary already on the target, and
use that instead of building the binary with Fuego.

Several people have mentioned that their test binaries are already installed
on the target with their embedded distro, and they would prefer to use those
instead of using the Fuego versions of the tools.

The mechanism needs to allow a test to specify the program name, as well
as possible locations?

This could either be done prior to each test's build phase, and then skip
the build phase automatically, or it could be done by a fuego "install"
check, and have all the test program paths for a target recorded.
This most primitive way would be to add a path for each test to the
board file.  But I much prefer autodetection.

Notes [edit section]

= Notes =
Should there be a global flag to indicate whether to use fuego-built
test binaries or pre-built (distro-based) test binaries?

I hate to add more state to the system.

The function [[function_is_on_target|is_on_target]] fulfills most of the
requirements for this issue. 

backlink

Fuego Issues List

; backlink: [[Fuego Issues List]]