Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Modified & Improved wxWidgets Project Wizard
Biplab:
--- Quote from: ascxaxsvcbsxbbqvcxqsbcvxs on February 08, 2007, 04:34:03 pm ---is it possible for 2 consecutive pages?
--- End quote ---
Yes! It's possible and it' very easy to do. :)
But I'll discuss with Other C::B devs before I commit any changes as it involves a reorientation. So you may have to wait. :)
Biplab:
Latest Changes:
* Added support for wxWidgets 2.9.x (CVS Branch). This is for the users who want to use latest wx CVS branch code.
* Added PCH support for GCC in Linux. This was missing since I started work on it. But I didn't notice that missing feature.Committed in Revision 3593. :)
Pecan:
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.
Biplab:
"wxWidgets is built in debug mode" option was removed and now the debug target is linked against debug version of wx libs and release versions are linked against release lib of wx.
I've added this page sometimes back to allow developers more fine control over the way a project is generated. If you check the last option Set Target Types (For Advanced Users Only) in wx lib configuration page (the last screenshot in your post) you'll be presented with the following window.
What I propose is to add one more option (One checkbox) saying Use Debugging wx Libraries for Both Targets in this page for Advanced Users. If you check it, it'll add debug wx libs to both targets.
IMHO, putting these advanced options in a separate page would be less confusing for newbies. :)
Is it OK? But I'll make necessary changes tomorrow only as I'm quite busy with my studies today. :D
Regards,
Biplab
Pecan:
--- Quote from: Biplab on February 13, 2007, 06:11:47 am ---
What I propose is to add one more option (One checkbox) saying Use Debugging wx Libraries for Both Targets in this page for Advanced Users. If you check it, it'll add debug wx libs to both targets.
IMHO, putting these advanced options in a separate page would be less confusing for newbies. :)
Is it OK?
--- End quote ---
Yes, thank you.
Just please make sure that __wxdebug__ is never set unless the user explicitly clicks on it.
As an example, I've been debugging CB for almost a year and a half now, and I've only needed __wxdebug__ once. It's very *seldom* used.
I suspect that it's only been used once this year, probably by the likes of Tim S. :D :D
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version