in reply to Re^9: Image-Magick on Strawberry Perl
in thread Image-Magick on Strawberry Perl

This re-opens the possibility that standalone Image::Magick ppm packages can be provided !!

For Image-Magick-6.89, using 8-bit rgb values (quantum depth = 8):
ppm install http://www.sisyphusion.tk/ppm/Image-Magick_.ppd --force

For Image-Magick-6.89, using 16-bit rgb values (quantum depth = 16):
ppm install http://www.sisyphusion.tk/ppm/Image-Magick.ppd --force

They expect to use the ImageMagick-6.9.2 that ships with them (and which is installed seamlessly).
YMMV if attempts are made to use them with another ImageMagick installation.

They both install a module named Image::Magick - which makes it tricky to have both types installed in the same build of perl.

None of this is explained on the repo website (yet) beyond that provided in the post-install scripts http://www.sisyphusion.tk/ppm/scripts/install_image_magick and http://www.sisyphusion.tk/ppm/scripts/install_image_magick_

Cheers,
Rob

Replies are listed 'Best First'.
Re^11: Image-Magick on Strawberry Perl
by davies (Monsignor) on Mar 04, 2020 at 09:56 UTC

    Thanks, Rob. I have been struggling to install I::M for Strawberry 5.30 on Win Server 2016. From a cmd prompt run as Administrator, I am getting two errors:

    C:\Windows\system32>ppm install http://www.sisyphusion.tk/ppm/Image-Ma +gick_.ppd --force Unknown option: force Installing package 'http://www.sisyphusion.tk/ppm/Image-Magick_.ppd'.. +. Bytes transferred: 127690 Files found in blib\arch: installing files in blib\lib into architectu +re dependent library tree cannot remove directory for C:\Users\Administrator\.ppm/Image-Magick_- +5188: Permission denied at C:/Strawberry/perl/vendor/lib/PPM.pm line +490.

    But it looks as though I::M is working. :-)

    Regards,

    John Davies

      Thanks for the feedback davies.
      I'm not sure that --force is really an unknown option. However, with perl-5.30.0, use of --force should no longer be needed.

      I think the attempt to remove C:\Users\Administrator\.ppm/Image-Magick_-5188 is just a post-installation cleanup whose failure should not affect the I::M functionality.
      I've come across that problem before, and never really worked out the mechanism by which permission is denied.
      You can probably delete that directory manually if it actually exists && you want to get rid of it.

      Annoyingly I'm not even able to successfully use ppm here, owing to some mysterious http access restrictions - so I can't test things out myself.

      Cheers,
      Rob