It only took me most of the afternoon to sort out, which I suppose isn't too bad, but I managed to compile win XP executables using pp -o.
The executable uses things like Net::HTTP and Crypt::SSLeay so it was nontrivial, and GPG to boot.
My machine here at work has MS .Net Framework installed but I also had to install the Microsoft Visual C++ toolkit 2003 and the Platform SDK for windows XP SP2, then I had to heavily hack PATH to include all the oddly named and located binary paths. Then I had to copy missing includes and librarys into the vcc-tk directory (lots of duplicates only a handful are actually needed).
Judicious use of windows search (and its annoying user interface), vcvars32.bat (ensure its in your path) and the links provided in the relevent thread of the perl.par newgroup made it possible.
most of the problems boil down to MS tools putting libraries and executables all over the shop, and you having to specify the paths and/or move them around. Searching google and your own machine for the missing or broken file will eventually yield an environment that will compile binaries for your platform that should run on XP SP2.
Of course the easy way is to use the ready-built binarys of parl and pp that autrijus provides.
Of course without AS I'd have to jump through even more hoops when using perl on WIN32.
Re:all because AS par ppm is over a year old
simonflk on 2004-11-10T01:01:00
I use a perl compiled with gcc to create my own PPMs. I've been able to create PPMs for PAR, Wx, XML::LibXML and others with relative ease. And they all work with a regular ActivePerl.
Re:all because AS par ppm is over a year old
TeeJay on 2004-11-10T14:14:41
annoyingly I now find that there is an resolved dependancy when it runs at the clients site.This has lead me to a handy tool via google tho : dependency walker which gives you nice dependency trees for your dll or exe files on 'doze -- shame it doesn't allow you to fix or bundle them.
