Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Modified & Improved wxWidgets Project Wizard
Biplab:
wx lib configurations are conveniently grouped now. See the following screenshot for more details. The changes are Windows specific.
Committed in Revision 3570.
Thanks ascx.....
ascxaxsvcbsxbbqvcxqsbcvxs:
--- Quote from: mandrav on February 05, 2007, 03:53:11 pm ---
--- Quote from: ascxaxsvcbsxbbqvcxqsbcvxs on February 05, 2007, 03:04:06 pm ---One more question: after compilation & execution OK, i tried to add one character in the title of the window, an acute letter. I got the message "Illegal byte sequence".
--- End quote ---
GCC needs to be told the character set used in your code. The compiler option is named "-finput-charset" and takes the encoding as argument. The default value is "-finput-charset=utf-8" (if I 'm not mistaken).
--- End quote ---
With this option, must i compile wxWidgets, just my application, or both?
Is this option available in CB, like Settings|compiler? i didn't find it.
ascxaxsvcbsxbbqvcxqsbcvxs:
--- Quote from: Biplab on February 05, 2007, 04:36:30 pm ---wx lib configurations are conveniently grouped now. See the following screenshot for more details. The changes are Windows specific.
Committed in Revision 3570.
Thanks ascx.....
--- End quote ---
It is better, but for newbies, i think you should slightly modify the messages, to point out that
=> the first group represent the past (how wxWidgets was compiled)
=> while the second group is the future (what you want your project to be).
marlo_nl:
Hi Biplab,
I can confirm that your alternative method (described below) can be used to create a Debug Target based on a shared wxWidgets Debug Library and a Release Target based on a static wxWigets library.
--- Quote from: Biplab on February 04, 2007, 07:52:38 pm ---
For the time being you can use alternate method. Use workspace.
* First create one wx project with one lib config, le's say static-unicode-non-monolithic. Keep this project open.
* Create second wx project with another lib config, let's say dll-unicode-monolithic. You've to create it in a different folder.
* Now remove generated source (if you've ur own source) and add same source to both the projects.
* Now save the workspace from File > Save workspace menu. From next time onwards, open the workspace and code::blocks will load both the projects.
You can uncheck the appropriate target for appropriate projects. E.g., if you wish that the first project will be built in debug mode then uncheck release target during project creation.
I agree that my suggestion may not be the best one, but it should work. :D
Regards,
Biplab
--- End quote ---
For those who don't like to create two seperate projects to support a Debug Target based on a shared wxWigets library and Release Target based on a static wxWidgets library you can do the following:
* Use the method above.
* Carefully investigate the build options generated by the wxWidgets Wizard for both projects (Debug and Release).
* This will learn you how to merge (manually edit) the build options of a single project in such a way that it supports a Debug Target based on a shared wxWigets library and Release Target based on a static wxWidgets library.
Regards, Marlo
Biplab:
Thanks marlo_nl for the feedback. :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version