Re: Is Unicode character set a problem when compiling GTK sources?

Thanks Arnavion, re-compiling glib, pango and gtk with Multibyte and then re-linking dependent DLL's did not solve anything. stack overflow in gobject.dll damn bug is somewhere, but it denies to show it self. [?] On Tue, Feb 17, 2015 at 8:21 PM, Arnavion wrote: > (Re-adding codekiddy and Fan to

Re: Is Unicode character set a problem when compiling GTK sources?

(Re-adding codekiddy and Fan to To:) On Tue, Feb 17, 2015 at 11:18 AM, Arnavion wrote: > Compiling as either MultiByte or Unicode should not make a difference. > That setting only affects the use of unannotated Windows API, but > glib/gtk should already be using the W forms of those API (with an

Re: Is Unicode character set a problem when compiling GTK sources?

Compiling as either MultiByte or Unicode should not make a difference. That setting only affects the use of unannotated Windows API, but glib/gtk should already be using the W forms of those API (with an intermediate utf8<->utf16 step). MultiByte is probably there in the project files because it's

Re: Is Unicode character set a problem when compiling GTK sources?

On 17/02/2015 18:36, codekiddy wrote: (even Fan's projects which I'm using) which were set to Multibyte character set are now set to *unicode character set* Can you tell what consequnces could that have? I'm starting to think it would be better to re-compile everything with Multibyte instead be

Is Unicode character set a problem when compiling GTK sources?

Hello, I'm working on VS projects to build GTK and gtkmm, and by accident found this mail on google posted by Chun-wei Fan. (Hi Fan!) And that surprised me a lot because I set all my projects to use *unicode character set* (even