All- I have checked in changes so that you can compile by default against the ImageMagick 5.2 libs. 5.2 fixes "imperfections discovered in 5.1.1. " . Since the API of 5.1.1 is unique, I feel it unproductive to try to fix the opendx/IM5.1.1 combination. Unfortunately, at this moment, the only IM binaries out there for linux look to be 5.1.1 . If you download IM 5.2 source (www.imagemagick.org) and you "configure --enable-shared " then you can "make" and "make install" in the coders and magick subdirectories only, skipping potential complications with some of the components we don't use.
You can manually remove the #define MAGICK5 from dxmods/_im_image.c to get IM version 4 compatibility, but you should explicitly link the static libMagick.a to avoid generating "undistributable" binaries. If the magick folks don't stabilize their API and provide corresponding binaries we may need to statically link for all versions. I have encountered problems on RH 6.1 with opendx compiled against IM 5.2 (segfault in fgetc). I compiled on irix and used purify to determine that the magick and opendx code was clean. I would appreciate some results on other platforms (RH6.2, etc.) to refine where the problem lies... hopefully it is just my egcs being downlevel. One should be able to place the current _im_image.c into most any recent opendx tree and compile. The rest of the opendx cvs has been volatile lately, so if "gif" is the only problem you're trying to fix you might do just that. Pete "R. Lahaye" wrote: > Peter, > > Thanks. > > I'm still lost and I have no clue what's going wrong. > Here is what happens on my Linux PC: > > "Peter D. Kirchner" wrote: > > > > Is HAVE_LIBMAGICK set to 1 in include/dxconfig.h ? > > Yes. > > > Remove the (by now huge?) appendable .miff you've been writing on multiple > > tries. > > Uuh, well yes indeed; there's a .miff file created. Why is that? I have > no intentions of creating this miff file, neither have I told > WriteImage. > Where does this miff file come from? > Concerning your remark: hence I have no idea how to stop generating > the miff file !?!?!? > > > Type "Image Magick supported format" *exactly* in the WriteImage CDB > > format area. > > I've typed that in by hand. > (This option was not in the format pull down menu, though somebody on > this list > mentioned that it should be listed in the menu; not for me...). > > > AND specify (say) foo.jpeg as the name (let's try to get any IM format for > > now). > > ==> Error window: "Connection to server has been broken". > Is this because I don't know how to stop generating the miff file? > > > Then if successful try foo.gif . > > Despite the error, I tried gif anyway and got the same error message > as with the jpeg image. > > Does all this give a hint why it's not working on my PC? > > Thanks, > > Rob. > > > > "R. Lahaye" wrote: > > > > > David and others, > > > > > > Thank you for your replies, but ImageMagick is still invisible > > > in DX after compilation. (see at the bottom for what CVSMake and > > > configure reports when performed). > > > > > > Configure seems to find all support for ImageMagick, since all > > > checks get a "yes". The compilation then runs fine. > > > (I have ImageMagick-5.1.1-1 and ImageMagick-devel-5.1.1-1 rpm's > > > installed on my Linux RH 6.2 PC). > > > > > > The WriteImage module still has the same pull down menu (rgb, > > > r+g+b, tiff, pscolor/gray, epscolor/gray, gif, yuv, miff) > > > without mentioning ImageMagick!?!?! > > > > > > However, when I now choose "gif", the Message Window doesn't > > > pop up anymore, but instead the Error Window shows up with the > > > message: "Connection to the server has been broken". > > > > > > What could be wrong? > > > > > > Thanks, > > > > > > Rob. > > > > > > ===================================================================== > > > ./CVSMake : > > > configure.in:982: warning: AC_TRY_RUN called without default to allow > > > cross compiling > > > configure.in:1006: warning: AC_TRY_RUN called without default to allow > > > cross compiling > > > configure.in:982: warning: AC_TRY_RUN called without default to allow > > > cross compiling > > > configure.in:1006: warning: AC_TRY_RUN called without default to allow > > > cross compiling > > > > > > ./configure --with-magick : > > > [...] > > > configure: warning: no acceptable jni header generator found in $PATH > > > configure: warning: JavaDX will be skipped during compilation due to > > > limitations. > > > [...] > > > checking for ImageMagick support ... > > > checking for magick/magick.h... (cached) yes > > > checking for GetImageInfo in -lMagick... (cached) yes > > > checking if ImageMagick package is complete... yes > > > [...] > > > ===================================================================== > > > > > > "David L. Thompson" wrote: > > > > > > > > If everything compiles correctly, you will get a new option in the > > > > pulldown menus named ImageMagick. If you didn't get this, then your > > > > configure did not pick up the ImageMagick correctly. > > > > > > > > Make sure that you delete config.cache in your dx directory and then > > > > reconfigure. Watch to make sure that ImageMagick gets a yes > > > > option--then try and compile.
