Page 1 of 1

Posted: 2006-04-01T18:09:06-07:00
by magick
Our standard answer to Windows compiler/run-time problems is to build one of the Magick++ demos found in c:\Program Files\ImageMagick-6.2.6-Q16\Magick++_Demos. Build the button demo and run. Most likely it will compile and run. You can then use this project as a template for your own project.

Another standard answer for minimizing dependacies under Windows, is to build ImageMagick as an "uninstalled" static multi-threaded project. The project is uninstalled by default unless you specifically uncomment UseInstalledMagick when running the configure program and editting magick-config.h. When you package ImageMagick for redistribution with your project just put all the configuration files and the library in the same folder. ImageMagick should find them at run time. You can verify by setting the MAGICK_DEBUG environment variable to configure. When you run ImageMagck it displays where its looking for its configuration files.

Posted: 2006-04-04T12:13:44-07:00
by magick
Try adding
  • using MagickLib::GetQuantumInfo;
to Magick++/lib/Magick++/Include.h. That should fix the problem.

Posted: 2006-04-05T13:57:36-07:00
by magick
Did you build ImageMagick from source or are you using the pre-compiled binaries? If the latter, it will always check the Windows registry since it was built with UseInstalledMagick defined. ImageMagick will look in the execution path of the program for any dll's to load only if UseInstalledMagick if not defined. This is done as a security measure to prevent someone from installing a nefarious ImageMagick DLL on a Windows box.