Hi.
I think I`ve got a contribution to C::B`s collection of example projects — namely, GUI-enabled app bundle for OS X ≥ 10.6. Not just a single executable file, but a full-fledged app with an icon, version information, human-readable name alias, and a bunch of other perks of Mac integration.
The only obstacle that remains is that Mac apps are not actually files, they are directories, and to create an app means, first and foremost, to create its directory structure.
This can be easily dealt with in pre-build steps.
However… here`s my problem: when the user orders C::B to clean the project, only the executable module gets erased, leaving the now-useless app corpse untouched.
The question is: how can I make the 'clean' target to actually clean what it has to?
I know that C::B supports custom makefiles, but that`s slightly an overkill for the task as I see it.