Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Modified & Improved wxWidgets Project Wizard
Biplab:
Another update to the wizard.
Changes:
* Supports Pre-compiled headers for BCC 5.5.1 and MSVC 8.
* Wizard CPP files are modified to support PCH.
* "Use the debugging libraries" option have been disabled in Windows part. This option is no longer necessary (See screenshot below).
* DECLARE_EVENT_TABLE(); in main.h file has been changed to DECLARE_EVENT_TABLE() This is necessary to avoid error while compiling with BCC.
* msvcrt.lib is now added as /NODEFAULTLIB in Debug target of MSVC 8 to avoid warning messages in some cases.
Known Issues:
* PCH support does not work with MSVC 6 or 7.1
* wx_pch.h file is included in the CPP files and also force included in case of GCC and MSVC. I have kept the force include option as some devs want this to remain. To support Borland, wx_pch.h have been added to CPP files itself. In future this option will be modifed as per CB devs and other users decision.
Please post your valuable feedbacks. :D
P.S. - I was trying to include support for MSVC 7.1 also. But my VC 7.1 installation is horribly broken. :evil: It wasted a lot of time.
[attachment deleted by admin]
MortenMacFly:
--- Quote from: Biplab on January 04, 2007, 05:30:43 pm ---
* Wizard CPP files are modified to support PCH.
--- End quote ---
Just my personal thoughts on that (nice!!!) work:
I wonder if it would make sense to separate the PCH feature into an own wizard. PCH isn't something possible for wx only (obviously). Do you think from your experience it would be possible to extract a "PCH enabling wizard" out of this one that can be applied to *any* project?
With regards, Morten.
Biplab:
--- Quote from: MortenMacFly on January 04, 2007, 07:16:59 pm ---
--- Quote from: Biplab on January 04, 2007, 05:30:43 pm ---
* Wizard CPP files are modified to support PCH.
--- End quote ---
Just my personal thoughts on that (nice!!!) work:
I wonder if it would make sense to separate the PCH feature into an own wizard. PCH isn't something possible for wx only (obviously). Do you think from your experience it would be possible to extract a "PCH enabling wizard" out of this one that can be applied to *any* project?
With regards, Morten.
--- End quote ---
Thanks for your comments. :D
A "PCH enabling wizard" is possible and I think that's a good idea, too. First I'm giving a rough sketch then I'll post my opinion.
My rough idea--
Page in Wizard ---------------------
[ ] Option 1
[ ] Option 2
[ ] Option 3
..
[ ] Select to enable PCH support
------------------------------------
Now the wizard shows PCH page,
PCH Settings -----------------------
Please Remember that PCH works well only when you have a large
number of static headers to include and your project CPP files have
consistent header declaration.
Improper use may increase Build time!!
[ ] Create PCH through (*.h / *.cpp) file
Browse [..................................]
PCH Handling
( ) Create & Use (Compiler Dependent)
( ) Use only (First C::B will create and then, will compile other files in Use only mode)
--------------------------------------
I would like to add it as a function in SDK so that the wizard can be called easily from any wizard.
If the Project involves huge amount of static headers, PCH would be beneficial. Otherwise not. Also the project/subproject cpp files should be consistent, otherwise regeneration of PCH file will kill the benefit.
But I feel the option may be misused by some users even for smaller and simpler projects. That would make them vent their anger on Code::Blocks itself. That's why I've put a warning message.
:D
Biplab:
A minor update to the wizard. This version has some fixes and improvements.
Changes in rev 3.3:
* Mssing preprocessor definition, USE_PCH, in project file of BCC has been fixed.
* Preprocessor definition in BCC for Unicode app has been changed to UNICODE from wxUSE_UNICODE as BCC doesn't likes it.
* Now option to select Advanced UI Library will NOT be available if wxWidgets 2.6.x is used
BCC produces a lot of errors if you are using wxUSE_UNICODE preprocessor definition. It fails as in some part of several wxWidgets headers #if <expr> has been used in place of #if defined(<expr>)
Manually editing them to #if defined clears the errors, but there are too many to modify.
Another useful info, BCC will fail to compile wxWidgets 2.8.0 in Unicode mode. To solve this, apply the patch to wx/filefn.h
http://cvs.wxwidgets.org/viewcvs.cgi/wxWidgets/include/wx/filefn.h.diff?r1=1.157&r2=1.158&diff_format=u
Latest revision is attached with this post. Please login to download. :D
[attachment deleted by admin]
rjmyst3:
I think wxUSE_UNICODE needs to be defined to a number
#define wxUSE_UNICODE 1
not just defined. That probably explains why BCC was upset.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version