Author Topic: Tool's output  (Read 181 times)

Offline AZ

  • Almost regular
  • **
  • Posts: 128
Tool's output
« on: October 12, 2019, 04:42:01 pm »
hello,
 i need to monitor the tty. for this i put together a small shell script (~/bin/monitor), that calls miniterm.py with a ${PROJECT_DIR} where it parses and pics port and baud params for the execution of miniterm.py :
Code: [Select]
~/bin/monitor ${PROJECT_DIR}

monitor:
Code: [Select]
//the boilerplate code removed
miniterm.py $baud $port

the challenge :
 a. when the xterm opens up and launches the "monitor", I can't select and copy the output to a buffer.
 b. as a workaround i thought i can redirect the output from the tool into a log. what params can i use in the "Tools"?
 c. ideally, i'd like to have the "monitor" to run one of the CB output windows ( like build log, valgrind etc). How can this be achieved?


My attempt to use "Tools+" and specifying the output to "Tools output window", got me :
Code: [Select]
execvp(~/bin/monitor, /home/az/Work/Arduino/Proj/) failed with error 2!

/code]



thank you.
« Last Edit: October 12, 2019, 04:50:49 pm by AZ »
CB: latest available from Jen's RPM repo for Fedora
Thread model: posix
gcc version 5.1.1 20150618 (Red Hat 5.1.1-4) (GCC)