>> We'll get a new release out in the next few days that has the configure >> program compiled with VS 2003 release.
Excellent news, the latest build, 6.5.0-10, uploaded today at 18.15 or so, has a configure.exe that works without the MFC debug libraries being installed. UTIL_NtMagick and UTIL_ImDisplay do in fact use MFC, and as such are not compilable using express editions of Visual Studio. This doesn't matter to me in particular, but would affect someone planning to work on ImageMagick itself, I would have thought. Just so you know. Also, from the perspective of setting up a project to use ImageMagick as a library, I have to say that it is not for the faint of heart - header files seem to be hidden away in various sub-folders, and determining which lib files are actually needed is similarly byzantine (the answer seems to be "all of them", so why give a choice?) A suggestion which would improve the client application development experience in those moments of setup would be to collate the header files into a single include/ImageMagick folder ala OpenGL, and to produce a compound (one might even say 'archive') lib file. Thank you for such a quick solution to my problem, and for an excellent imaging library. Tom. _______________________________________________ Magick-users mailing list [email protected] http://studio.imagemagick.org/mailman/listinfo/magick-users
