On Tue, Feb 24, 2009 at 06:30:14AM -0800, Michael G Schwern wrote: > Rafael Garcia-Suarez wrote: > >> I see two strategies: > >> > >> 1) Copy ext/ExtUtils-MakeMaker/lib/ into lib/ at some point early in the > >> build > >> process. > >> > >> 2) Jigger the ext/ build process so MakeMaker gets built first and > >> installed > >> into lib/ > > > > The first option looks more feasible, since the copying into lib is done > > via Makemaker-generated makefiles anyway. (IIRC) > > This should be all that is necessary: > > cp -r ext/ExtUtils-MakeMaker/lib/* lib/ > > Just need to know where to put it.
Makefile.SH, win32/Makefile, win32/makefile.mk, win32/makefile.ce and vms/descrip_mms.template I think. Whereas if the logic can end up in make_ext.pl, it only needs to be in one place. (My hope being that it would be possible to build everything in ext using -I options or the environment, against the not-yet-installed-in-lib MakeMaker. If that's not possible, it's still viable, as I'm not sure if anything other than the Makefile.SH generated Makefile supports parallel makes. Parallel makes are relevant, as one needs to create some sort of dependency rule to ensure that the copy of ext/ExtUtils-MakeMaker/lib/* fully completes before anything else wanting it starts) Nicholas Clark
