With help from the manual, the code and several forum entries I had success in remotly
compiling my project and getting the warning and error messages highlighted in the console window.
The main barrier breaker was the application plink.exe, which is part of the PuTTY
application (see http://www.chiark.greenend.org.uk/~sgtatham/putty/\).
This also makes it possible to connect to the serial port, but you have to use a saved
session from PuTTY.
Below is the complete command used:
c:\program files\PuTTY\plink.exe -ssh -pw password user@machine /bin/sh -e ./Setup_remote_variables && cd /net/rita/application/build && make
There where some problems with absolute path length in output filters, the real length is far
longer than is supported in the ouput filter. The solution was to use the "cd" command in the console and
then replace the relative linux/unix paths with relative windows path.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all
With help from the manual, the code and several forum entries I had success in remotly
compiling my project and getting the warning and error messages highlighted in the console window.
The main barrier breaker was the application plink.exe, which is part of the PuTTY
application (see http://www.chiark.greenend.org.uk/~sgtatham/putty/\).
This also makes it possible to connect to the serial port, but you have to use a saved
session from PuTTY.
Below is the complete command used:
c:\program files\PuTTY\plink.exe -ssh -pw password user@machine /bin/sh -e ./Setup_remote_variables && cd /net/rita/application/build && make
There where some problems with absolute path length in output filters, the real length is far
longer than is supported in the ouput filter. The solution was to use the "cd" command in the console and
then replace the relative linux/unix paths with relative windows path.