Code::Blocks Forums

User forums => Help => Topic started by: pplp on March 18, 2007, 02:57:13 pm

Title: No xterm trying to run console appliocation
Post by: pplp on March 18, 2007, 02:57:13 pm

Hi everyone

 I downloaded codeblocks latest svn (March 18 2007). I compiled it and installed it in Arch Linux. I tried to run (not debug) a simple Hello World program from the templates but I don't see any terminal opening. I see in Settings -> Environment that "Terminal to launch console programs" is set to "xterm -T $TITLE -e" and xterm is working perfectly. As shell I can see that is defined "/bin/sh -c". How can I fix this?

Title: Re: No xterm trying to run console appliocation
Post by: Pecan on March 18, 2007, 04:02:02 pm

Under the Messages Build Log you should see a msg like "Executing .." xterm or whatever.

What does it say it's trying to do. Anything?


Mine: SVN 3676 shows:

Code

Checking for existence: /home/pecan/proj/conio/conio
Executing: xterm -font -*-*-*-*-*-*-20-*-*-*-*-*-*-*  -T 'conio' -e 'LD_LIBRARY_PATH=.:$LD_LIBRARY_PATH /home/pecan/devel/trunk/src/devel/cb_console_runner "/home/pecan/proj/conio/conio" ' (in /home/pecan/proj/conio/.)

There's recently been a "War on Macros" that's kinda messed a few things up. You might want to revert to an earlier SVN (like above) if you want to execute or debug from Linux.

Eventually, the "War" will end, and it'll all work again.

Title: Re: No xterm trying to run console appliocation
Post by: pplp on March 18, 2007, 07:01:57 pm

Assuming that I look at the correct tab, the one named "Build log" I can see only this

Code

Checking for existence: /tmp/test/bin/Debug/test
Executing: "/tmp/test/bin/Debug/test" ' (in /tmp/test/.)
Process terminated with status 0 (0 minutes, 0 seconds)

Even if I press Build->Build and run.

I will try to install your version and I hope everything works.

Thank you :D

Title: Re: No xterm trying to run console appliocation
Post by: jarro_2783 on March 20, 2007, 12:43:58 pm

Mine did the same in windows yesterday, it looks like the latest revision has fixed it.