I finally figured out what was confusing me so much about this new wizard.
It was creating a __wxdebug__ type project when I thought it meant it was creating a CB debug project. Those are way too different things:
To get a widgets CB debug target, I have to change all the compile names, all the linker names, all the resource names and remove the __wxdebug__.
To get what is usually thought of as a CB debug project(which is what the overwheming majority of users will want), we'll have to tell the user to create a Release target and set it by hand to produce a debug project.
Not a good thing to have to tell anyone. It's going to cause a huge amount of confused traffic on this forum. I know right now that not too many people can be generating debug targets with this wizard, because I know that can't have debug versions of wxWidgets sitting around.
I suggest that you add a line in widgets library setting like:
wxWidgets is built in debug mode.
If checked, then generate the __wxdebug_ and append the 'd' to the file names.
If not, generate a "debug" target just like a "release" target but with the -g option and the warnings flags set.
