User forums > Using Code::Blocks

Compiler/Linker Options doesn't work in OSX 10.5

(1/2) > >>

frankmail007:
The compiler options `wx-config --cppflags` and linker options `wx-config --libs --debug=yes` seems not working under OSX 10.5. I have to manually add the search path and flags for compiler and linker. My codeblocks is compile from the latest 8.02 source code and my wxWidgets is 2.8.9. Does anybody have this problem?

By the way, I'm also trying to compile the latest source code from SVN. The bootstrap is simply failed:

-bash ./bootstrap /bin/sh^M: bad interpreter: No Such file or directory

I used vi to replace ^M by command %s/^V^M$//g. It also doesn't work. So I used bootstrap from 8.02 souce code. But it doesn't work again in configure:

configure: Creating ./config.stats
.infig status: error: cannot find input file: Makefile

Does anybody successfully compile the latest source code from SVN? Thanks

frankmail007:
Is it a bug?

eranif:

--- Quote ----bash ./bootstrap /bin/sh^M: bad interpreter: No Such file or directory
--- End quote ---
this is an EOL problem (End Of Line) bash expects '\n' while the file has '\r\n' (vi represents it as ^M)

run:

--- Code: ---dos2unix bootstrap
--- End code ---

Eran

frankmail007:

--- Quote from: eranif on October 01, 2008, 07:38:01 pm ---
--- Quote ----bash ./bootstrap /bin/sh^M: bad interpreter: No Such file or directory
--- End quote ---
this is an EOL problem (End Of Line) bash expects '\n' while the file has '\r\n' (vi represents it as ^M)

run:

--- Code: ---dos2unix bootstrap
--- End code ---

Eran


--- End quote ---

Thanks for your reply. Now the problem is `wx-config --cppflags` and `wx-config --libs` doesn't work. Under command line, it works. But in CB, it simply just ignore the flags. If I purposely remove the `, it will show the flag under compiling log.

afb:
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...

Navigation

[0] Message Index

[#] Next page