[OctDev] Re: [Octave-cvsupdate] octave-forge/main/image imread.m,1.11,1.12 imwrite.m,1.8,1.9

[Stefan v. d. W. <st...@su...>]

ImageMagick unfortunately also links to libjpeg and libpng to read
those two formats.  Also, the libMagick API has changed from version 6
to 8 -- some distributions like Debian keep to v6 while others like
Mandrake have moved to v8.

Whichever way, the API example given on their webpage compiles but
doesn't run with either versions!

St=E9fan

On Sun, Jul 24, 2005 at 08:24:11AM -0400, Andy Adler wrote:
> St=E9fan,
>=20
> That sounds like a good idea. On the other hand, a better implementatio=
n
> would be to write an oct file  to link to the imagemagick libraries dir=
ectly.
>=20
> After that, the only reason to have jpgread etc is for users that don't=
 have
> libmagick.a.
>=20
> What do you think?
>=20
> Andy
>=20
> On 7/24/05, Stefan van der Walt <st...@su...> wrote:
> > Last time I checked, the pipes implementation was much slower than th=
e
> > file approach for large images.  Can you verify whether this is still
> > the case?
> >=20
> > I have made some fixes to pngread and jpegread, which I will submit
> > soon.  Then, we can use those functions in imread.m to load JPGs and
> > PNGs, but revert to ImageMagick otherwise.
> >=20
> > Regards
> > St=E9fan