animation.xq test crashes using Windows installer

Image Module is out in Release 2.5
ImageMagick should not be shipped with Module.

Very soon (certainly before 2.7) we need to figure out how to ship the image module without bundling ImageMagick. That means documenting that the user must install it, and doing the best that we can to find it. Also, the image module should fail gracefully with a clear error if the user tries to run a query using it but it can't find ImageMagick.

Modules are failing because need the instruction:
InitializeMagick();

after adding this instruction we should not include ImageMagick libraries, we should encourage the user to install latest version of ImageMagick.

That's weird - why do the tests work from ctest, if we're missing a required initialization?

From documentation: http://www.imagemagick.org/Magick++/

Please note that under Windows (and possibly the Mac) it is necessary to initialize the ImageMagick library prior to using the Magick++ library. This initialization is performed by passing the path to the ImageMagick DLLs (assumed to be in the same directory as your program) to the InitializeMagick() function call. This is commonly performed by providing the path to your program (argv[0]) as shown in the following example:

int main( ssize_t /*argc*/, char ** argv)
{
  InitializeMagick(*argv);

This initialization step is not required under Unix, Linux, Cygwin, or any other operating environment that supports the notion of "installing" ImageMagick in a known location.

That's... really weird. Are you aware of other tools that work that way on Windows?

Regardless, very interesting. I agree that this call will be necessary to support users installing ImageMagick themselves. I do wonder, however, how we are going to call InitializeMagick() if we need to provide the path to the ImageMagick installation. How are we supposed to find the ImageMagick libraries on the user's system at runtime?

From ImageMagick:

If argv is not available use
InitializeMagick("");

http://www.imagemagick.org/discourse-server/viewtopic.php?f=1&t=9581

No, I'm not aware of other tools that work that way yet for Zorba...

Finally I found the page I want to show:
http://www.graphicsmagick.org/Magick++/

>>>
If you don't have the path to your executable, then pass NULL and usually the library will be found anyway. Besides helping to find the GraphicsMagick DLL/library and configuration files, InitializeMagick() initializes all of the semaphores and data necessary for a multi-threaded program to be completely thread safe. This step used to be optional, but it is now absolutely required. Failure to initialize GraphicsMagick will result in an application crash.

Ohh.. nevermind, previous page is from another library, anyway, seems that ImageMagick behaves the same way...

Well, here are the facts:
- Zorba crashes because we ship an incomplete version of ImageMagick, not because we don't initialize ImageMagick
- If we don't ship ImageMagick we receive a "DLL Load Failed" error, that was a known issue
- What we need is an ImageMagick verification code that checks that ImageMagick is installed, if not, then Zorba throw an error in a more natural way.

Branch updated, please test