Modified & Improved wxWidgets Project Wizard

[Biplab]

OK, thanks, it worked.
You should group these 4 major parameters in the same panel, and make this obvious. For example, gray the options that do not correspond to the compiled wxWidgets, if not too complex to do.

It's a good suggestion. I'll group them. 

Out of these 4 major parameters, 1 parameter is decided by the target(s) you've checked in the Compiler selection page. I'll group the remaining 3 parameters.

[ascxaxsvcbsxbbqvcxqsbcvxs]

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".

[Biplab]

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".

Probably you need to compile your app with Unicode build of wxWidgets lib. 

[ascxaxsvcbsxbbqvcxqsbcvxs]

i did it from the beginning. That's why i'm little bit surprised!

[mandrav]

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".

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).

[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]

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".

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).

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]

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.....

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.

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. 

Regards,

Biplab

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. 

[saddam le pion]

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".

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).

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.

Good question! as it seems to be here lots of non-english developers, who develop non-english applications. This implies almost automatically source codes with "special" letters, so source codes with utf8.
So we want our CB to automatically accept utf8 (or having to parameter it just one time for all), not having to parameter the compiler manually for each source file of each application...

[thomas]

GCC uses UTF-8 unless told otherwise...

[ascxaxsvcbsxbbqvcxqsbcvxs]

GCC uses UTF-8 unless told otherwise...

1) I installed CB version 3565 on XP
2) I installed wxWidgets 2.8.0 and compiled it with gcc with unicode => OK
3) use of the wizard to generate a basic application with unicode => compile and execute OK with gcc
4) Then without modifying any CB option anywhere, i just add the special letter é to the title of the windows:

original line, generated by the wizard
azeFrame* frame = new azeFrame(0L, _("wxWidgets Application Template"));
modified line, for beginning to test the unicode support
azeFrame* frame = new azeFrame(0L, _("wxWidgets Application Templateé"));

no other modification except this character => i got the compile message "Illegal byte sequence".

5) If i suppress this character => compile OK
6) I've now tried several times with last build 3577 => same problem, but the error message is now
"converting to execution character set: Invalid argument"

[ascxaxsvcbsxbbqvcxqsbcvxs]

GCC uses UTF-8 unless told otherwise...

with Dev-C++ I have no problem with the special letters: so i don't think it is a compiler problem.

[yesidh]

I'm using mingw compiled wxWidgets using the ./configure not using the makefile.gcc that comes with wxWidgets because someone it didn't work dor me. The make file generated me the files and I copied to the $wxWIN/lib/gcc_lib

The point is that the libraries generated are like this: libwx_base-2.8.a

Seeing the wizard.script in the codeblock, I can see that the wizard looks for something like libwxbase28.a according to my setting. So I modified the 3586 SVN and it is now working. Am I the only one with this issue?.

Thanks.