Re: [Kicad-developers] I hate even more wxString

2013-04-29 Thread Lorenzo Marcantonio
On Sun, Apr 28, 2013 at 09:01:11PM +0200, Lorenzo Marcantonio wrote: ... now, I know that this can be fixed using GetChars, but WHY it worked on 2.8 and nobody else with 2.9 encountered this??? Uhm *maybe* I have found the problem. It seems to be caused by wx built with UTF8 and/or STL usage.

Re: [Kicad-developers] I hate even more wxString

2013-04-29 Thread Maciej Suminski
On 04/29/2013 08:18 AM, Lorenzo Marcantonio wrote: On Sun, Apr 28, 2013 at 09:01:11PM +0200, Lorenzo Marcantonio wrote: ... now, I know that this can be fixed using GetChars, but WHY it worked on 2.8 and nobody else with 2.9 encountered this??? Uhm *maybe* I have found the problem. It seems

Re: [Kicad-developers] I hate even more wxString

2013-04-29 Thread Lorenzo Marcantonio
On Mon, Apr 29, 2013 at 08:40:06AM +0200, Maciej Suminski wrote: I had a similar problem - it was enough to turn off --enable-stl (or explicitly add --disable-stl) for wxWidgets library. Unicode toggling did not change much. Confirmed. It's the --enable-stl that breaks compilation (no idea of

[Kicad-developers] I hate even more wxString

2013-04-28 Thread Lorenzo Marcantonio
Every wx releases something works slightly different... I'm trying to use wx 2.9.4 (installed with the wxPython distribution) Configured OK, building woes: static int wxCALLBACK MyCompareFunction( long aItem1, long aItem2, long aSortData ) { wxString* component1Name = (wxString*) aItem1;