>Your problem about using UTF16 is related to the fact you are using
>windows os and not linux or unix or macos x. All the others use utf-8
>EXCEPT WINDOWS.
Isn't that what I was saying? It is horrid that Microsoft uses UTF-16 because,
just like their software, it bloats everything to twice the s
On 04/30/2016 11:25 PM, Andrew Robinson wrote:
> My initial request for help in this forum was that main(argc,argv) only
> returned garbage instead of the command line when using the 32-bit version of
> GTK+ v3.18 on a 64-bit Windows7 OS. This forum was unable to offer any expert
> help or advice o
Thank you Lucas, for submitting this post. MXE seems very interesting and I
feel compelled to do some more research into it.
On 5/2/2016 at 3:36 AM, Lucas Levrel wrote:
>(copy to OP in case he's already unsubscribed, apologies for duplication
>if he's not)
>
>Le 30 avril 2016, Andrew Robinson a
On 05/02/2016 12:36 PM, Lucas Levrel wrote:
> […]
>
> I'm not an expert programmer and when I wanted to compile for Windows
> the software I developped in Linux, I couldn't achieve a satisfactory
> result (using the -mwin32 or -mwindows flag gave either a clumsy
> additional command window, or yie
(copy to OP in case he's already unsubscribed, apologies for duplication
if he's not)
Le 30 avril 2016, Andrew Robinson a écrit :
Now my new problem I had was either locating a Win32 version of GTK+ greater
than v3.18 or locating a version of libglib.dll greater than v2.40. It isn't
going to ha
