Thats why I looking forward at Enviroment Variables settings per target [...]
I guess I'm still missing something here: You said previously that you would like to pass specific variables per-target. Why don't you use user variables for this as they should get replaced also for the commands?! Thus in the command write something like:
call_my_batch.bat $MyUserVar
And setup the user variable for this target e.g. as "123.234.123.234"...
Then inside the batch file you can do with it whatever you want, e.g.
@echo off
echo The command line provided is: %1.
the_app.exe "%1"
With regards, Morten.
Here is some kind tutorial to make it work on Windows 5.0 and later:
You will need PuTTY package. You can get it here (http://www.chiark.greenend.org.uk/~sgtatham/putty/).
Compiler batch files
@echo off
set SELF=%~n0
set LOGIN=%1
shift
set REMOTE=%1
shift
set SRCDIR=%1
shift
:next
if "%1" == "" goto end
set PARAMS=%PARAMS% %1
shift
goto next
:end
set PARAMS=%PARAMS:\=/%
c:\bin\putty\plink.exe -C -batch -l %LOGIN% %REMOTE% cd %SRCDIR%; %SELF% %PARAMS%
At C::B you need to make copy of "GNU GCC Compiler" and name it "Remote GNU GCC Compiler".
Go to Settings>Compiler and Debugger>Remote GNU GCC Compiler>Other>Advanced and add
$(login) $(remote) $(srcdir)
to each profile after first variable.
At C::B in Build options you need to set custom variables login, remote, srcdir for targets.