New Mac OS X (x86/10.4) build

[afb]

I've uploaded two versions of Mac OS X builds to BerliOS. ("incoming")

• codeblocks-rev2898_macx86.zip
• codeblocks-rev2898_macppc.zip

The first is a Universal Binary compile with GCC 4.0 for Mac OS X 10.4,
the second is a PowerPC binary with GCC 3.3 for Mac OS X 10.2 - 10.3.

It has been tested on Mac OS X 10.3.9 and 10.4.7, but on PowerPC only.
(still has a couple of known bugs, but should open files and compile...)

News in this release:

• added icon for .cbp projects (but double-click to open doesn't work yet)
• restructured internally, dropped the shell wrapper and bin/lib/share dirs

Patch to make it find the "Resources" dir of the bundle, where the helper files are:
http://developer.berlios.de/patch/?func=detailpatch&patch_id=1399&group_id=5358

Otherwise it has all the patches from the previous build (see the other Topic)
It would be nice if these could be integrated into the main Subversion soon ?

[Game_Ender]

I second the subversion integration of patches, but I am sure Mandrav has noticed them and just been to busy to put them in.  Thanks for the work and keeping the OS X wiki page up to date with your progress.  I will give this build a try when I get to work on monday (Intel iMac 10.4).

[mandrav]

Actually, I committed most of them this morning...

[takeshimiya]

afb: do you think it would be better to save the configuration on ~/Library/Application Support/CodeBlocks/ instead of ~/.codeblocks?

[afb]

afb: do you think it would be better to save the configuration on ~/Library/Application Support/CodeBlocks/ instead of ~/.codeblocks?

It depends... (on which side of the split-minded Mac OS you are on)

First of all, "Application Support" would be OK for e.g. the plugins
- but it is hardly the place to store the user's configuration, is it ?

If the application is in /Developer/Applications/CodeBlocks.app,
then it makes sense to have the config in ~/Library/Preferences.

But if the application is  instead located in /usr/local/bin/codeblocks,
then I don't see any problems with having it stored in ~/.codeblocks ?

And if switching to ~/Library, then it needs to be in Apple plist format.
I think it will be much more portable to just leave it in ~/.codeblocks.

BTW;
The reason why I am using plain dylibs instead of frameworks,
is because I didn't feel like including 20 megs of wx headers.

It would make sense for /Library/Frameworks/wx.framework,
but it doesn't for CodeBlocks.app/Frameworks/wx.framework...