Legacy ImageMagick Discussions Archive

IM 6.6.3.0 Q16 Mac OSX Tiger.

When you update (from source) from an older release, say 6.6.2.x to a new (non-minor) version, like 6.6.3.0, the custom filters from MagickFilterKit-1.0.0 are not automatically moved to the appropriate directory. One has to copy them from the old directory.

For example:

In the older release where they were compile:

/usr/local/lib/ImageMagick-6.6.2/modules-Q16/filters
/usr/local/lib/ImageMagick-6.6.2/modules-Q16/filters/analyze.la
/usr/local/lib/ImageMagick-6.6.2/modules-Q16/filters/analyze.so
/usr/local/lib/ImageMagick-6.6.2/modules-Q16/filters/ellipse.la
/usr/local/lib/ImageMagick-6.6.2/modules-Q16/filters/ellipse.so
/usr/local/lib/ImageMagick-6.6.2/modules-Q16/filters/getColors.la
/usr/local/lib/ImageMagick-6.6.2/modules-Q16/filters/getColors.so
/usr/local/lib/ImageMagick-6.6.2/modules-Q16/filters/reduceColors.la
/usr/local/lib/ImageMagick-6.6.2/modules-Q16/filters/reduceColors.so
/usr/local/lib/ImageMagick-6.6.2/modules-Q16/filters/sphere.la
/usr/local/lib/ImageMagick-6.6.2/modules-Q16/filters/sphere.so


But in the new release after upgrading:

/usr/local/lib/ImageMagick-6.6.3/modules-Q16/filters
/usr/local/lib/ImageMagick-6.6.3/modules-Q16/filters/analyze.la
/usr/local/lib/ImageMagick-6.6.3/modules-Q16/filters/analyze.so


Can this be fixed easily?

To automatically support custom ImageMagick filters, we would need a complex script that identifies new filters or coders and then modify the autoconf / automake build files. In addition the user would need the latest releases of the autoconf / automake / libtool distributions to reconfigure the make files / build environment. We do not see this enhancement happening anytime soon, if ever.

OK. Thanks for the reply. At least I know now that I will have to copy the files from one release to another.

The filters should be re-compiled for the new release. Not simply copied.

Sure the filters compiled for the previosu release will work, most of the time, but eventually something will not match the library. Perhaps some identifier or method name will be using a different number that represents that name.

Of course the less the filter relies on core library the less likely a 'conflict' will happen. But still it should be re-compiled
at lease for Changes of the first three numbers.

This is why it is difficult to incorporate automatic transfer. IM does not know how to compile your filters unless it is fully re-configured using 'autoconf' etc.

Thanks for the explanation. I will keep that in mind and do so.

Fred