Re: [perl-win32-gui-hackers] Any release soon? (was: CVS Commits - bug fixes and enhancements)
Jez, I was going to mail you off-list, as I was playing with the MinGW build last week to try to get the size down, and I succeeded in reducing the size of my GUI.dll for the current head build from 3104 KB down to 979 KB (which is only 100k or so bigger than the VC build of the 1.0 source). I did the following to my Makefile: (1) remove -g from LDDLFLAGS (2) remove -g -O2 from CCFLAGS (3) change -O2 to -Os in OPTIMIZE The '-g' is the biggest culprit, which adds huge amounts of extra stuff to allow debuggers (and particularly gdb) to run well with the code. The '-Os' optimises for size (it's nearly the same as -O2 according to the docs), and shaves around 200KB off the size compared to '-O2' I suspect that it might be better to change these values in Comfig_m.pm, as then you'd get the benefit for any other perl modules that you build. If someone can explain to me how to build the documentation, then I'd be happy to put together a release candidate. (I've also got a couple more bug fixes that are not currently checked in). Regards, Rob. Jeremy White wrote: In short, can we please release a new version of Win32::GUI in the near future? I would be happy to test a release candidate to make sure it works with TGL. I dropped a mail to Laurent to see if he could do a build a week or so ago - but no reply. Mingw produces larger dll files than the MS compiler that Laurent uses, but I'm sure Rob or myself could put a build together using Mingw? Cheers, jez. --- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 ___ Perl-Win32-GUI-Hackers mailing list Perl-Win32-GUI-Hackers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/perl-win32-gui-hackers
Re: [perl-win32-gui-hackers] Any release soon? (was: CVS Commits - bug fixes and enhancements)
I did the following to my Makefile: (1) remove -g from LDDLFLAGS (2) remove -g -O2 from CCFLAGS (3) change -O2 to -Os in OPTIMIZE The '-g' is the biggest culprit, which adds huge amounts of extra stuff to allow debuggers (and particularly gdb) to run well with the code. The '-Os' optimises for size (it's nearly the same as -O2 according to the docs), and shaves around 200KB off the size compared to '-O2' Nice. I'll have a play with these options. If someone can explain to me how to build the documentation, then I'd be happy to put together a release candidate. (I've also got a couple more bug fixes that are not currently checked in). To create the HTML docs, I run: perl dodoc.pl perl dohtml.pl in Win32-GUI\docs directory - although I've no idea how these files would be included in the PPM:) Cheers, jez.
Re: [win32gui] Re: [perl-win32-gui-hackers] Any release soon? (was: CVS Commits - bug fixes and enhancements)
To create the HTML docs, I run: perl dodoc.pl perl dohtml.pl in Win32-GUI\docs directory - although I've no idea how these files would be included in the PPM:) Thanks - I was a bit confused by the fact that dodoc.pl seems to have options for building html too. I've got a PPM built from my local source, and I've made the following changes to what seems to have been done before: (1) Moved document install from C:\Perl\html\lib\Win32\GUI to C:\Perl\html\site\lib\Win32\GUI. I believe that this is the correct place to install the html files, and results in other documentation generated with pod2html linking to the right pages. (2) Add the contents of the CVS samples directory to C:\Perl\site\lib\Win32\GUI\demos (i.e. in a sub directory of the install location, in a directory called demos.) This is consistent with what the Tk package does, but I'd be happy to call it samples if that's the general consensus. (3) I've added some notes on performing a PPM installation into the Readme.txt file We need to agree a version number for the next release. I would propose 1.01 - I think that we should be using a 2-digit second part of the version number to be CPAN friendly (See perldoc perlmodstyle), and don't see that there's enough change to justify anything other than incrementing the minor version by the smallest increment. If we can agree the version numbering issue,. I'd be happy to make a release candidate available from my website. I'll also write up my notes on building the PPM, so others can do it. I've added a note to my TODO list to look at adding a PPM target to the makefile (so we can just do nmake ppm (or whatever). I've also noticed that many of the document links with a page are broken, but don't have time to explore this further right now. Regards, Rob.
