C::B working on Intel MAC OS X, but requires Makefile changes

[sethjackson]

AngelScript? Code::Blocks doesn't use that anymore...... :?

Great. one less thing to worry about... :-)

Wonder what else happened since last time ?

Lots.
Anyways C::B uses Squirrel for scripting now anyways.

[afb]

Okay, hope it won't be another 6 months until I check in again :-)

(Hmm, still no RC3 ? I would have thought that to be out by now)

[Paco.Blasco]

Thanks. It works better than rev2411, but Rosetta is not working fine with this executable.
When I used it I can n ot create new projects, it can not open (right) created projects....It doesn't compile....
Am I the only one that it is trying to work with C::B on IntelMacs????

[afb]

I am currently using Mac OS X 10.3 on PPC still, since Tiger has been so buggy for me.

[Paco.Blasco]

Ops...I'm working on Tiger with IntelMac.
:?

[afb]

Once I get the funds for a new Mac, I'll upgrade to Tiger and Intel as well...
Meanwhile I am running Fedora Core instead, which works just fine on Macs.

[afb]

Thanks. It works better than rev2411, but Rosetta is not working fine with this executable.

I'll see if I can build a Universal Binary as well, that might work better for you.

[mandrav]

Then I have problems. Is it possible to send me your app bundle (compressed)?
I can use it as a base to compile C::B with C::B.

I have uploaded rev 2886 to BerliOS, was hoping to get it deployed ?

http://developer.berlios.de/project/showfiles.php?group_id=5358&release_id=9217

Oops, sorry I missed it. It's in the Files section now. Thanks .

[Paco.Blasco]

Thanks. It works better than rev2411, but Rosetta is not working fine with this executable.

I'll see if I can build a Universal Binary as well, that might work better for you.

It will be very good if you can build an Universal binary. At the moment, I have no too much solutions to get a C::B for my Mac. PPC version has a lot of problems (due to Rosetta I think), and Intel version is not compiling too much right (it is unusable).
Anyone can help us to create a check list to begin to solve all problems of C::B on Tiger/Intel?
It is complicated for anyone that has been never debug the C::B code.
I need a small help in order to begin to patch C::B.

Thx.

[afb]

I don't see any real problems with an Universal Binary / on Intel,
just need to get it wrapped and then tested on a real Intel as well.

But I would also be interested in what kinds of problems people are
seeing, if they are specific to Intel or if they're more of generic Mac.

[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]

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

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 Select Expand


ld: object_file illegal reference to symbol: ***
defined in indirectly referenced dynamic library: ***


[afb]

'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

These issues are fixed in the 2890 build, which should be available on BerliOS shortly.