Re: Why cannot ActiveState build Wx ?

Did you read previous posts of mine? This one killed me. Don't use one from ActiveState. Use wxperl.co.uk source. You must use Windows XP SP 3 or above. Terrible C compiling issues >>> C:\Perl\bin\perl.exe Makefile.PL compilet-2112487424.c Command line warning D4002 : ignoring unknown option '-dl

Wx Memory Leak (was: "Memory Leak (in Wx::Perl::ProcessStream)?")

> Cornelius Bartke wrote: >> However, while processing the output, W:P:PS seems to allocate memory >> and running a rsync process again does not reuse the memory. Per >> 10.000 lines of STDOUT processed, my process grows by 45MB (Debian >> Lenny, perl 5.10, Wx v0.92, wxWidgets 2.6.3.2, on winXP it

Why cannot ActiveState build Wx ?

I was trying to understand why ActiveState does not package Wx by itself. here is the latest log http://ppm4.activestate.com/MSWin32-x86/5.10/1000/M/MB/MBARBON/Wx-0.92.d/log-20090902T150346.txt linked from here: http://ppm4.activestate.com/idx/WW...WX.html Can someone please look at it and try

RE: wxSashWindows

Hi Johan, What you say is true, but for me I was looking for a multi-panel fixed form, However I'm not sure that I chose the right path anymore. I feel that using Fixed sizes in sash windows defeats the point of sizers in widgets. I wonder whether I should just have used a GridBagSizer with emb