Legacy ImageMagick Discussions Archive

None of these issues were related to VS 2015. The include <> issues would have affected any compiler. Probably most people put the headers on the include path. I didn't do that since I was just giving it a try. The remaining issue is probably due to my using a high level of warning flags. Again, not ...

I downloaded Magick to try it on a minor image editing task I had (I was successful, and Magick appears to be very well done). I am using VC 2015 and had to make some minor header changes to get a clean compile. As far as I can tell, all of these changes should be standard. I also had a problem when ...