[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: merging imread and imwrite
From: |
John W. Eaton |
Subject: |
Re: merging imread and imwrite |
Date: |
Thu, 31 Jan 2008 15:50:34 -0500 |
On 31-Jan-2008, Thomas Treichl wrote:
| There won't be a problem on MacOSX -- it's just a question about how many
| library dependencies should be solved before building ImageMagick and use
that
| for Octave? Sure, the best thing would be 'all' but I think then we would at
| least double the size of an Octave standalone binary application just because
of
| graphics libraries?! So I'm out of ideas here -- what is the best middle
course?
If we only linked the ImageMagick libraries with the .oct files that
need them, then the Octave binary itself would not be larger, but yes,
it is somewhat more complicated to build a fully functional Octave
distribution if there are more dependencies.
OTOH, if all we are doing is reading some image files, maybe ImageMagick
is more than we need. Are there other portable libraries available
that support a reasonable number of image formats and that just read
and write without being full image processing libraries?
jwe
- merging imread and imwrite, John W. Eaton, 2008/01/28
- Re: merging imread and imwrite, Søren Hauberg, 2008/01/29
- Re: merging imread and imwrite, John W. Eaton, 2008/01/30
- Re: merging imread and imwrite, John W. Eaton, 2008/01/31
- Re: merging imread and imwrite, David Bateman, 2008/01/31
- Re: merging imread and imwrite, Thomas Treichl, 2008/01/31
- Re: merging imread and imwrite,
John W. Eaton <=
- Re: merging imread and imwrite, Søren Hauberg, 2008/01/31
- Re: merging imread and imwrite, Thomas Treichl, 2008/01/31
- Re: merging imread and imwrite, John W. Eaton, 2008/01/31