On Tuesday 01 August 2006 12:24, Joshua Hoblitt wrote: > On Mon, Jul 31, 2006 at 10:30:36PM -0700, chromatic wrote:
> > * What's the best way to integrate building this module from the main > > Makefile? Should it be part of that process? > That depends. Are any of the standard regression tests going to require > this module? For now, no. I'd like to have the option of running the standard regression tests through it, but it's not stable enough yet. > > * Where should the built module go, and how can we make that work in a > > cross-platform way? Copying the two (for now) necessary files out of > > blib/lib appropriately is probably the right answer. > > I'd say let Module::Build handle the install. The install process can > invoke Module::Build if it's to be part of the default install. How about when just building Parrot but not installing it? I'd also like to run the Parrot::Embed tests as part of the normal Parrot test suite. -- c
