The codeblocks.cbp file is currently like a makefile: it contains a separate target for each module and builds all of the core C::B.
This is one way to use.
We could use another way though:
We could create a separate project for each module. Basically make each target contained in codeblocks.cbp a separate project and wrap all projects in a workspace.
We could configure the new projects' targets (configurations) like this:
- Unicode WX DLL - Debug
- Unicode WX DLL - Release
- Unicode WX DLL - Profile
- Ansi WX DLL - Debug
- Ansi WX DLL - Release
- Ansi WX DLL - Profile
So, if anyone wanted to work only on a specific plugin, he/she could open the plugin's project and work on it. No extra burden. And choose which wx DLL to use (unicode/ansi).
Or if a developer wanted to profile the code-completion plugin, he/she could enable profiling only for this plugin (actually profiling must only be enabled for one module or else gmon.out gets overwritten).
So, what do you think? Should we make those changes or should we leave it as it is now?
(now that I think of it, we could have both ways)