Bug #10747 2007-03-27 11:59

afb

wxMac: need to add resource fork or application bundle

As with all other wxWidgets programs, codeblocks needs either a resource fork or an application bundle to launch on Mac OS X - or it will start in the background and not receive any events (e.g. no mouse clicks, no keys)

The wiki page mentions this, but in order to not confuse new users and to help when debugging Code::Blocks we should add a resource fork (and an icon) to bin/codeblocks during the installation phase so it works...

Category
Application::WrongBehaviour
Group
 
Status
Closed
Close date
2007-03-29 11:34
Assigned to
afb

History

afb 2007-03-28 08:25

Also applies to the wizard for new wxWidgets projects

biplab 2007-03-28 09:54

@afb, I've no Mac experience. So please feel free to modify the wizard as needed.

afb 2007-03-28 09:59

I intend to :-) Seriously, it's just a post-build script addition for wxMac...

Just looking into another issue where `wx-config ...` doesn't find my own wx-config (in /usr/local) but Apple's crappy old wx-config (in /usr). I think this is because CB is only passing PATH=/usr/bin, considering that's where gcc is located but doesn't account for other programs in backticks.

afb 2007-03-28 12:05

Commited the changes to the wxWidgets wizard. Using resource forks since otherwise I would need to a) create bundles b) teach CB how to launch bundles. Since wxWidgets refuses to add functionality to launch programs without either resforks/bundles, this is as good as it gets...

biplab 2007-03-28 12:51

Thanks for the update. :-)

afb 2007-03-29 11:34

Fixed in revision 3793 (workaround might not be needed for wxWidgets 2.8 but it still is with wxWidgets 2.6.4 so might as well always do it...)