ImageMagick has never been able to keep a stale API and this is why the GraphicsMagick library exists as a fork of ImageMagick.. In any case imread/imwrite have been ported to Octave itself using the GraphicsMagick libraries and will appear in a 3.2.x release. It would still be nice to have this fixed for the next octave-forge release so that the 3.0.x versions of Octave can build with ImageMagick 6.4.0, as it appears that it should be compatible with both 6.4.0 and earlier versions.
I'll look at it tomorrow when I'm on a machine with an SVN tree of octave-forge Cheers David -- View this message in context: http://www.nabble.com/__magick_read__--is-broken-for-imagemagick-6.4.0-tp18697988p18698543.html Sent from the octave-dev mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
