> At Thursday, 28 February 2002, Glenn wrote: > > >Now I've downloaded and compiled the new version. Boy was I surprised!
jean bosco muzatsinda wrote: > > Hi, > How did you proceed to download and compile? > I'm knew to this matter of things ( win32::GUI)and I'm experiencing > some problems. > Thanks, > > Jean Although this was a private message (inappropriate) I'm replying back to the list, because there may be a number of others that have never compiled Win32::GUI, that now suddenly have the desire to. It was my first time to ever compile a perl module, but really, it isn't too hard when things are set up right, I guess, and it seems that Aldo has things set up right. The following is what I did to download and compile: Download: used web browser, went to http://data.perl.it/, found the link for the source ( http://dada.perl.it/Win32-GUI-0.0.665.tar.gz ), and fetched it to my local hard drive, I used d:\. Using cmd.exe, I Then "gunzip Win32-GUI-0.0.665.tar.gz" Then "tar xvf Win32-GUI-0.0.665.tar" Then "cd d:\Win32-GUI-0.0.665" I used my favorite text editor, emacs, to look around. It appears that although the code has been enhanced and restructured into multiple source files, that the documentation has not yet been enhanced in any way, and also not the sample code. Then I had to experiment to see how to compile. Since I'm using ActiveState's perl, which is reportedly compiled using MS VC, I figured I'd need to get that on my path. And I remembered that when I had installed MS VC, it had told me about a batch file that can put it on the path (doesn't need to be on the path when you use the MS IDE). And I remembered seeing, over and over again on various perl lists, the comment that when using MS VC, you have to use "nmake" instead of "make". And the theoretical process for installing modules is documented as the sequence of commands: perl makefile.pl make make install So I wrote the following batch file: call "c:\program files\microsoft visual studio\vc98\bin\vcvars32.bat" perl makefile.pl nmake nmake install Upon executing it from the command line prompt, where my current directory was d:\Win32-GUI-0.0.665, it seemed to do the trick. I then attempted to run a couple scripts for which I had already set up shortcuts, and lo and behold! they used the new version of Win32::GUI ! With the surprise reported earlier. -- Glenn ===== Remember, 84.3% of all statistics are made up on the spot.
