User forums > Using Code::Blocks

Console app run/debugging for MacOSX

<< < (2/5) > >>

afb:
On second thought, it might not be possible to do that in the wxMac version of Code::Blocks - you might need to run the wxGTK version of it, or just apply/wait for the Terminal.app patch.

bnilsson:
I guess what might be missing for me is that CB is not aware of any $DISPLAY.
Can I set this somewhere?
"Compiler..Settings -> Custom variables" is not doing the trick.

(And the patch did not do any difference, still xterm)

--- Quote ---Checking for existence: /Users/bnilsson/Documents/Programming/Active/CB_projects/dxfcnv/dxfcnv
Executing: xterm -T 'dxfcnv' -e DYLD_LIBRARY_PATH=.:$DYLD_LIBRARY_PATH "&quote&"/Users/bnilsson/Documents/Programming/Active/CB_projects/dxfcnv/dxfcnv"&quote&"  (in /Users/bnilsson/Documents/Programming/Active/CB_projects/dxfcnv/.)
Process terminated with status 1 (0 minutes, 0 seconds)
--- End quote ---

afb:

--- Quote from: bnilsson on November 30, 2006, 10:25:05 pm ---I guess what might be missing for me is that CB is not aware of any $DISPLAY.
Can I set this somewhere?
"Compiler..Settings -> Custom variables" is not doing the trick.
--- End quote ---

I set it in /etc/profile.


--- Quote ---(And the patch did not do any difference, still xterm)
--- End quote ---

It's a preference, so if you have an old setting of xterm
you probably want to change it to the new "osascript..."

bnilsson:
Non comprendo:
--- Quote ---It's a preference, so if you have an old setting of xterm
you probably want to change it to the new "osascript..."
--- End quote ---
Please explain?

afb:
In the C::B Settings > Environment dialog:
("Terminal to launch console programs in:")

For wxMac (patched), this should be:

--- Code: ---osascript -e 'tell app "Terminal" to do script "$SCRIPT"'
--- End code ---

For wxGTK (e.g. linux), it is instead:

--- Code: ---xterm -T $TITLE -e
--- End code ---

Worst case, wiping the preferences works.

Navigation

[0] Message Index

[#] Next page

[*] Previous page