Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
C::B working on Intel MAC OS X, but requires Makefile changes
Auria:
I remember i had downloaded the previous version you posted (24 something?) i don't quite remember this version, but i think it was more functional than this one :? almost nothing reacts. 'new file' doesn't react, 'new project' doesn't either. trying to open various 'configure' options trigger no reaction either. So it looks nice, but is yet impossible to use on its own...
However i was able to create a file in a third-part text-editor, then open it in code blocks and build. The text in the console and build messages is so small it's almost impossible to read
i'm on PPC, mac OS X 10.3.9 ( if i was just a little bit better at programming i could trying helping, but i'm not :( ) Well good job anyway keep trying i'll try helping if i can :lol
afb:
--- Quote from: Auria on August 23, 2006, 09:06:54 pm ---I remember i had downloaded the previous version you posted (24 something?) i don't quite remember this version, but i think it was more functional than this one :? almost nothing reacts. 'new file' doesn't react, 'new project' doesn't either. trying to open various 'configure' options trigger no reaction either. So it looks nice, but is yet impossible to use on its own...
--- End quote ---
Yeah, I'm trying to run it through the debugger here (in debug build) to see what I can find...
Just thought I'd upload, once I got it to build ;-)
afb:
The 2890 revision looks a whole lot better for project/file "Open"...
So I guess it was just one of those "nightly" / reorganization issues.
Or it was the zip files containing old (!) xrc files when doing a build,
and it got better when wiping all the old files out with a clean build.
afb:
The LDFLAGS="`wx-config --libs`" ./configure workaround doesn't work for Universal builds, as it will pass the -isysroot /Developer/SDKs/MacOSX10.4u.sdk to GCC twice - making it cry and killing the build.
Will patch all the Makefile.am for the plugins instead.
The issue is that you can't link with libcodeblocks.dylib, without also linking with the wxWidgets libraries that it (indirectly) requires. A little Mac OS X quirk there...
--- Code: ---ld: object_file illegal reference to symbol: ***
defined in indirectly referenced dynamic library: ***
--- End code ---
afb:
--- Quote from: Auria on August 23, 2006, 09:06:54 pm ---'new file' doesn't react, 'new project' doesn't either. trying to open various 'configure' options trigger no reaction either. So it looks nice, but is yet impossible to use on its own...
However i was able to create a file in a third-part text-editor, then open it in code blocks and build. The text in the console and build messages is so small it's almost impossible to read
--- End quote ---
These issues are fixed in the 2890 build, which should be available on BerliOS shortly.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version