Problem solved, more or less. The issue is with gcc compiler. Apparently
the gtkmm bundle package is build with gcc-4.6.2, and some hack or other is
done to get glib/glibmm to compile.
If you try to compile and link your program with a different gcc version (I
tried 4.7.0 and 4.7.2) the ustring
I suggest even recompile gtkmm, had to do that here!
Eu sugiro ainda recompilar o gtkmm, tive que fazer isso aqui!
2013/9/9 Edscott Wilson edscott.wilson.gar...@gmail.com
Problem solved, more or less. The issue is with gcc compiler. Apparently
the gtkmm bundle package is build with
usually better
to just not trust prebuilt libraries at all.)
From: gtkmm-list [mailto:gtkmm-list-boun...@gnome.org] On Behalf Of Edscott
Wilson
Sent: Tuesday, September 10, 2013 7:43 AM
To: Alcione Ferreira; gtkmm-list@gnome.org
Subject: Re: Glib::ustring in mingw
Problem solved, more or less
Hey,
If I use Glib::ustring in Linux, everything works fine. But when I
compile the program under mingw in windows, segv invariably follows any
GLib::ustring. Methinks the culprit would be the internal utf-8 conversions
which distiguish Glib:ustring from std:string.
If I try to specify
