aboutsummaryrefslogtreecommitdiff
path: root/tests/script/bootstrap/chipkit.sh
diff options
context:
space:
mode:
authorSZEDER Gábor <szeder.dev@gmail.com>2017-09-26 17:36:38 +0200
committerSZEDER Gábor <szeder.dev@gmail.com>2017-09-27 00:14:57 +0200
commitc49af21700b413b6efdc3d75193b885896b56dd9 (patch)
treec6f4e72ab8519e3d44ab95d4d14426bdb7780a9c /tests/script/bootstrap/chipkit.sh
parent9708e8265d02ec4bc89533a06ec74c0aedec03c3 (diff)
Recognize serial monitors with full path in MONITOR_CMD
When assembling the command line for the various supported serial monitors, MONITOR_CMD must match the name of one of the supported commands to be recognized. Serial monitors given with leading path components are not recognized, and a command like make MONITOR_CMD=~/src/picocom/picocom monitor errors out as the fallback monitor command is executed instead of the picocom-specific one. However, sometimes it's necessary to specify a supported serial monitor with its full path, because e.g. the user wants to tests a freshly compiled version before installing it. Sure, the user could just run the serial monitor directly, but that's cumbersome because he has to pay attention to use the right baud rate and USB port. So strip all leading path components, if present, from MONITOR_CMD using the 'nondir' make function before checking whether it's one of the supported serial monitors. This way commands like the above would just work. While at it, remove the single quotes around 'putty': they are both unnecessary and inconsistent with similar constructs throughout Arduino.mk.
Diffstat (limited to 'tests/script/bootstrap/chipkit.sh')
0 files changed, 0 insertions, 0 deletions