tiwag, if I understand correctly, you 're only concerned about the "debug/release" page? If that's the case then all that's needed is a more elaborate page allowing you complete control over the targets to create...
correct
i think we should not drive the users into a project-layout, which is inconvenient when it comes to extend the project
as it is with the "debug/release target" approach.
the problem which exists with that "debug/release target" project setup is,
that when you have several projects for building your application,
you have to take care of all needed settings (e.g. wx lib type, threading model, ...) to be the same in all projects
and you have to edit them manually for each project.
When you have a project-layout as i proposed in the first posting,
you start with a debug version and when the project reaches a state,
where you can think of a release version, you only copy the project file
and edit the debug and optimization flags and you can build your release
application without any other modifications.
With the "debug/release target" project setup, this is not easily possible,
until all targets in all projects have the same name (at this time no automatic check is possible)
and when it comes to build them in different object files folders, there is currently also the bug
in the CB- workspace-build-system.