I noticed that by default my console program is not running after I hit ctrl+f10. I just see opening and immedietly closed xterm.
I got command C::B was trying to run and tryed to exec in my opened xterm:
xterm -T test-cpp -e /bin/sh -c /usr/bin/cb_console_runner /home/sayd/projects/test-cpp/bin/Debug/test-cpp
But it closed too.
I fixed command, now it runs as it should be:
xterm -T test-cpp -e /bin/sh -c "/usr/bin/cb_console_runner /home/sayd/projects/test-cpp/bin/Debug/test-cpp"
So I decided to fix C::B too:
Index: src/plugins/compilergcc/compilergcc.cpp
===================================================================
--- src/plugins/compilergcc/compilergcc.cpp (revision 4603)
+++ src/plugins/compilergcc/compilergcc.cpp (working copy)
@@ -1748,8 +1748,11 @@
// -- Csh Programming Considered Harmful
command << DEFAULT_CONSOLE_SHELL << strSPACE;
}
+ // each shell execution must be enclosed to "":
+ // xterm -T X -e /bin/sh -c "/usr/bin/cb_console_runner X"
+ // here is first \"
+ command << _T("\"");
}
-
// should console runner be used?
if (target->GetUseConsoleRunner())
{
@@ -1776,6 +1779,10 @@
{
command << execStr << strSPACE;
command << target->GetExecutionParameters();
+ // each shell execution must be enclosed to "":
+ // xterm -T X -e /bin/sh -c "/usr/bin/cb_console_runner X"
+ // here is first \"
+ command << _T("\"");
}
else
{
Don't know is it ideal to just take and patch, but it may be a place to start fixing problem.