User forums > Using Code::Blocks

Compiler/Linker Options doesn't work in OSX 10.5

<< < (2/2)

frankmail007:

--- Quote from: afb on October 06, 2008, 08:20:22 am ---Are you sure that `wx-config` is in the Code::Blocks search path ?
An easy way to check is to use the absolute path instead of "wx-config"

One problem is that "the resource hack" doesn't work anymore in Leopard,
so there is now no way to launch the program from a "bin" (needs bundle)

But it should still compile/link fine, just that it doesn't respond to any events.
Both the p2 release of 8.02 and the nightly build (svn 5211) work OK here...

--- End quote ---

I copy wx-config to /usr/bin. By the way, I also tried the CB windows version. It seems to have the same problem. ( I can't use the shell version wx-config come with compiled wxWidget. Instead, I can only use wx-config.exe. It only work if I specify `wx-config.exe`.)

afb:

--- Quote from: frankmail007 on October 07, 2008, 05:21:30 am ---I copy wx-config to /usr/bin.
--- End quote ---

There should have already been a wx-config there (the old one that comes with the system)
So you might want to keep your own version of it somewhere else, like in /usr/local/bin ?

It's just a symbolic link, so it doesn't matter much if you've overwritten it...
But normally /usr and /System is reserved for software installed by Apple.

So, does the copying make it work ?

frankmail007:
Yes, I rename the old wx-config to wx-config.org. But it still doesn't work unless I replace the `wx-config` with its result copied from shell commnd line.

afb:

--- Quote from: frankmail007 on October 08, 2008, 05:06:44 am ---But it still doesn't work unless I replace the `wx-config` with its result copied from shell commnd line.

--- End quote ---

OK, so it still doesn't work with the config program in `/usr/bin/wx-config` ?.
Probably not a PATH problem then, if that isn't in the path then what is... :-)

What about using the full path ?

Navigation

[0] Message Index

[*] Previous page