|Think about Loose Coupling|
Re^4: RFC: Compiling C/C++ based Modules under ActiveState using MinGWby syphilis (Chancellor)
|on May 10, 2007 at 17:20 UTC||Need Help??|
you were focusing just on the build portion of the process
Not really ... the difference seems to be that I'm suggesting we run '*make install' (where '*' is either 'd' or 'n'), whereas you're suggesting that, having built the module, one then builds a PPM, then installs it via 'ppm install ...".
I hope my above response was not taken as an attempt to denigrate your contribution
Good Heavens !!, no :-)
I'll get around to writing a review of PPM:Make or a tutorial on building PPMs
Excellent idea, and I encourage you to do so. I've built a few PPM's from time to time - by tar'ing and gzip'ing the blib (using GnuWin32's tar and gzip) and by hand-creating the ppd file. I'm sure that PPM::Make simplifies the process.
One thing I wonder about (having never used PPM::Make) is how it handles the situation where a dll needs to be installed via a post install script. See, for example the line <INSTALL EXEC="PPM_PERL" HREF="http://theoryx5.uwinnipeg.ca/ppms/scripts/install_pdl">install_pdl</INSTALL> at http://theoryx5.uwinnipeg.ca/ppms/PDL.ppd. Does PPM::Make catch the need to insert that 'INSTALL EXEC' entry ? Does it write the post install script ? (Just a couple of issues for you to address when you come to write that tutorial.)
Thanks for your input.