Where can i set the cb_console_runner arguments ?
I want cb_console_runner to execute:
konsole -T hello -e /usr/bin/cb_console_runner /home/op/devel/codeblocks/hello/bin/Release/hello
instead of:
konsole -T hello -e '/usr/bin/cb_console_runner LD_LIBRARY_PATH=$LD_LIBRARY_PATH:. /home/op/devel/codeblocks/hello/bin/Release/hello
i'm not able to figure out, where it gets the LD_LIBRARY_PATH from
regs wally
It's hardcoded, and a change would not really make sense.
It means that shared libs are searched first in the LD_LIBRARY_PATH of the system (if any), than in the executables directory, and thean in the paths configured with ldconfig.
i figured out that the problem is not the LD_LIBRARY_PATH stuff,
but my konsole. Seems i screwed up something with the bashrc
or whatever.
When i run with "xterm -T $TITLE -e" in the environment-settings, it works.
When issuing the following in an konsole outside CB:
konsole -T hello -e /usr/bin/cb_console_runner LD_LIBRARY_PATH=$LD_LIBRARY_PATH:. /home/op/devel/codeblocks/hello/bin/Release/hello
it also works.
but the line created by CB does not work and give the same termination error
(Process terminated with status 254 (0 minutes, 0 seconds))
konsole -T hello -e '/usr/bin/cb_console_runner LD_LIBRARY_PATH=$LD_LIBRARY_PATH:. /home/op/devel/codeblocks/hello/bin/Release/hello '
the only difference is ['] in the beginning and [ '] (apostroph without space and apostroph with space.
I do not know what's the reason and i try to survive with the ugly xterm.
regs wally
The issue should be fixed in svn r5449.
Thank you for this info !
Quote from: wally on February 11, 2009, 08:36:02 PM
Thank you for this info !
To be more clear, the issue with the quotes is fixed, but that's not the cause for the returncode 254.
With the quotes the "konsole" closes immediately without stopping.
254 is returned because of the "-T" paramter,tha does not exist for "konsole" (at least not in kde4).
running C::B SVN 5456 on KDE3.
Seems the quotes and the "-T" option are not the reason of my problem.
konsole --help reports the "-T" option as window title.
A:
following command in xterm and in konsole starts a new konsole as expected.
konsole -T hello -e /usr/bin/cb_console_runner LD_LIBRARY_PATH=$LD_LIBRARY_PATH:. /home/op/devel/test/hello/bin/Release/hello
B:
running from inside C::B: with env konsole -e
hangs and require to kill konsole process
C:
running from inside C::B: with env xterm -e
works as expected with window title cb_console_runner
D:
running from inside C::B: with env konsole -T $TITLE -e
Checking for existence: /home/devel/test/hello/bin/Release/hello
Executing: konsole -T hello -e /usr/bin/cb_console_runner LD_LIBRARY_PATH=$LD_LIBRARY_PATH:. /home/devel/test/hello/bin/Release/hello (in /home/devel/test/hello/.)
Process terminated with status 254 (0 minutes, 0 seconds)
E:
running from inside C::B: with env xterm -T $TITLE -e
Checking for existence: /home/op/devel/test/hello/bin/Release/hello
Executing: xterm -T hello -e /usr/bin/cb_console_runner LD_LIBRARY_PATH=$LD_LIBRARY_PATH:. /home/op/devel/test/hello/bin/Release/hello (in /home/op/devel/test/hello/.)
Process terminated with status 0 (0 minutes, 4 seconds)
works as expected with window title hello
F:
on my system also is kde4.1installed.
I have konsole 1.6.6(using KDE 3.5.9) in path /opt/kde3/bin/konsole
and
konsole version 2.1 using KDE 4.1.3) in /usr/bin/konsole
C::B running in KDE 3.5.9 environment.
/usr/bin/konsole --help does not report the -T option, exactly as Jens said.
setting environment to /opt/kde3/bin/konsole -T $TITLE -e
works nice now.
I assume the kde4 /usr/bin/konsole will works without the -T $TITLE parameter
as "konsole -e" environment setting in KDE4 environment.
regs wally