On Mon, 22 Mar 1999, Larry Moore wrote: > >i have put the Magick.pm file in my site_perl folder, but there is a folder > >called t in the download....do i simply have to copy the contents to the t > >folder in the MacPerl folder? or is it more complicated than this? > > > The t folder usually contains scripts that test whether the module was > correctly installed and works properly. > Looks like mail got hosed over the weekend... :-) Anyway, I just wanted to point out, since Adam's getting into PerlMagick, that one needs to have ImageMagick, the C library, built and available to start with. The PerlMagick.xs is just the XS *interface* to all that functionality. ImageMagick has already been ported to MacOS in a limited way. The basic tools are available as apps. So building a library that supplies most of the functionality shouldn't be too gross. The distributions are sizeable, and so a shared library suitable for MacPerl wouldn't be too small, either. This is one of those situations that poses some problems for Mac porting wrt CPAN. If all the functionality was shared between the Perl and XS code, then we could build it and put it up on CPAN no problem. But for the cases where the functionality is mostly in a C library someplace, and the XS is just interfacing, I think there is less support for us putting the binaries up on CPAN. Yes, there are counter-examples - XML-Parser is one, but Larry Wall had a hand in this module, the distribution encapsulates the C library, so it is sort of OK. If there is enough demand for this thing I can take a look and build it, and at least supply instructions. Apple MPW is free and one ought to be able to build a shared PerlMagick lib with MrC. Arved ==== Want to unsubscribe from this list? ==== Send mail with body "unsubscribe" to macperl-modules-request@macperl.org