Hmmm ... disappointingly, it seems that these dll builds of ImageMagick make use of the Windows registry to locate the coder dlls.
That quickly kills any enthusiasm I might have had for creating ppm packages. (Just makes me want to vomit, actually.)

I see that Jean-Louis' Bribes repo provides builds (perl-5.16.x and earlier only) that don't rely on the registry. He has simply placed the coder dlls in the blib/auto/Image/Magick folder - which apparently works for him ... but doesn't work for me.
Does anyone know how he gets that to work ?

Update: Just for the record, building Image::Magick for Strawberry Perl seems to be not too difficult.
Having downloaded and installed http://www.imagemagick.org/download/binaries/ImageMagick-6.9.2-5-Q8-x64-dll.exe into C:\_64\im (making sure to tick the box that would install headers and libraries) I cd'd to \_64\im\ImageMagick-6.9.2-Q\lib and ran:

gendef ../CORE_RL_magick_.dll * [../CORE_RL_magick_.dll] Found PE+ ima
+ge

gendef ../CORE_RL_magick++_.dll * [../CORE_RL_magick++_.dll] Found PE+
+ image

gendef ../CORE_RL_wand_.dll * [../CORE_RL_wand_.dll] Found PE+ image

dlltool --kill-at --input-def CORE_RL_magick_.def --output-lib libCORE
+_RL_magick_.a

dlltool --kill-at --input-def CORE_RL_magick++_.def --output-lib libCO
+RE_RL_magick++_.a

dlltool --kill-at --input-def CORE_RL_wand_.def --output-lib libCORE_R
+L_wand_.a

dlltool --kill-at --input-def CORE_RL_magick_.def --output-lib libMagi
+ckCore.a
[download]

It's quite likely that only the first and last of those 7 commands actually needed to be run.
Following that, I ran:

set PATH=%PATH%;C:\_64\im\ImageMagick-6.9.2-Q8
set CPATH=C:\_64\im\ImageMagick-6.9.2-Q8\include;%CPATH%
set LIBRARY_PATH=C:\_64\im\ImageMagick-6.9.2-Q8\lib;%LIBRARY_PATH%
[download]

Then cd to the top level folder of the PerlMagick-6.98 source and run 'perl Makefile.PL', 'dmake test' and 'dmake install'.
The only test that failed was t/wmf/read.t.

Cheers,
Rob