User forums > Using Code::Blocks

Mac os X bundle

<< < (2/2)

Auria:
The rez thing should NOT be used. it is for legacy stuff (classic apps)

It's much better to build an app bundle. Quick example of how to do it:

Target > Build Options > Pre/post build steps

Pre-build steps:

--- Code: ---mkdir -p $(TARGET_OUTPUT_DIR)/MyApp.app/Contents/MacOS
mkdir -p $(TARGET_OUTPUT_DIR)/MyApp.app/Contents/Resources

--- End code ---

post-build step:

--- Code: ---cp $(TARGET_OUTPUT_FILE) $(TARGET_OUTPUT_DIR)/MyApp.app/Contents/MacOS

--- End code ---

This is dirty and incomplete, but if you continue in that direction, add an info.plist file, fix executable location instead of copying it, etc. you can probably get it working quite well enough

If you can make a wizard out of that, please share it, it would be awesome  :D

Fenk:
I'm sorry for reviving such an old thread, but I'd really like to know if that wizard finally got made. XCode works too well to be struggling with C::B on Mac OS X  :D (although it is a wonderful alternative for most Windows IDEs). Did you guys get an automated solution to this?

afb:

--- Quote from: Fenk on December 09, 2009, 11:52:12 am ---I'm sorry for reviving such an old thread, but I'd really like to know if that wizard finally got made.

--- End quote ---

That would be a: "no" (but patches welcome)

http://svn.berlios.de/svnroot/repos/codeblocks/trunk/src/plugins/scriptedwizard/resources/wxwidgets/wizard.script

Navigation

[0] Message Index

[*] Previous page