I've tried using the installations from the ImageMagick website. The problem with those is PAR-Packer (pp) cannot create executables to access ImageMagick correctly. I keep getting NoDecodeDelegateForThisImageFormat errors. I believe it's because the Imagemagick.org installations require settings within the Windows registry to access these decoder DLLs. And pp does not handle registry settings when it packs the exe file
The ImageMagick on bribes.org don't require the registry settings to be there.
Has anyone out there gotten the bribes.org version to work, even just to execute IM functions in a regular perl script, that is not in a pp executable?
| [reply] |
I've tried using the installations from the ImageMagick website. The problem with those is PAR-Packer (pp) cannot create executables to access ImageMagick correctly. I keep getting NoDecodeDelegateForThisImageFormat errors. I believe it's because the Imagemagick.org installations require settings within the Windows registry to access these decoder DLLs. And pp does not handle registry settings when it packs the exe file
The ImageMagick on bribes.org don't require the registry settings to be there.
Nope, all wrong. PAR/pp cannot detect all the prerequisites, so it doesn't pack them all. This is easily tested by overriding %PATH% and attempting to run pp generated .exe. If some dlls aren't packed, you'll get an error message, so you go back and add those.
Has anyone out there gotten the bribes.org version to work, even just to execute IM functions in a regular perl script, that is not in a pp executable?
Bribes did not pack all the prerequisites.
You can get his ppm to work by installing a compatible (same version bribes uses) binary from http://www.imagemagick.org/ and making sure to add it to your path (the installer does this through the registry).
| [reply] |
Unfortunately, imagemagick.org doesn't have available binaries for v6.5.7. I attempted to compile a binary installer from source using Visual Studio 2010, but there are issues. Running everything up to executing BuildImageMagickObject.cmd is fine. I get a "This file requires _WIN32_WINNT to be #defined at..." after this point. Perhaps I should get earlier version of VS.
I tried just building the DLLs which are placed into the Release\bin directory\. I copied the contents of that directory minus any .pdb files and other intermediate files into the C:\Perl\site\lib\auto\Image\Magick directory where Bribes put its IM files. Then add it to my PATH env variable, as well as MAGICK_HOME.
It didn't work. I'm still getting this:
Can't load 'C:/Perl/site/lib/auto/Image/Magick/Magick.dll' for module Image::Magick: load_file:Recursion too deep; the stack overflowed...
What other prerequisites are needed?
| [reply] |