User forums > Using Code::Blocks

Additional actions for target 'clean'?

(1/1)

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

BlueHazzard:
is it desired to run this clean step on every build process or only on the clean command?
for every build process use the pre build step

for only clean, i am afraid that codeblocks can not do this at the moment. You can add a feature request on the sourceforge ticket system

Maybe you can hack around this with some scripting: http://wiki.codeblocks.org/index.php/Scripting_commands

hidefromkgb:
Got it.
Anyway, I`m getting negative feedback on the stability of C::B under Mac 10.12 (whereas I`m on 10.11.6), so I bit the bullet and made the project build from an external makefile.
https://github.com/hidefromkgb/msu3-waves
In its current state it`s way too superfluous for a sample, with all this OpenGL and especially the ObjC-by-means-of-C99 stuff, but potentially it won`t take long to rewrite this in ObjC and throw away everything except an empty window.
Would you want me to?

Navigation

[0] Message Index