>> Wow - that's exactly what I need! Does MakeMaker just automatically run >> anything named *.PL that it finds? That's perfect! >> > > So... it's a bit tedious to find, but the documentation for > ExtUtils::MakeMaker ( > http://search.cpan.org/~mschwern/ExtUtils-MakeMaker-6.62/lib/ExtUtils/MakeMaker.pm) > states that any .PL file in the distribution's root directory will be run > (find under the PL_FILES key). Module::Build has similar functionality. :-)
Perhaps I should look (at some point) at moving some of the configuration logic out of Makefile.PL and into a CPP.pm.PL file for Inline::CPP. CPP.pm.PL could read the existing CPP.pm and write out the changes much like the way Makefile.PL does it, but under the direction of ExtUtils::MakeMaker instead of directly under Makefile.PL. I don't really see an advantage though, but if it's "the right way to do it", I suppose it couldn't hurt to make a change. That reminds me, there's another solution to the OP's question. His module could be adapted to simply read a configuration file on startup, and that config file could be built at configuration/install time. Config::General could help to avoid rolling a new solution. -- David Oswald daosw...@gmail.com
