AMIDE: Amide's a Medical Imaging Data Examiner

Note: old questions no longer relevant to the current release of AMIDE can be found here

Installation Issues

• I've installed AMIDE, but the help menus don't seem to be giving any help. Also, when AMIDE starts up, it gives the following error message:

         GnomeUI-WARNING **: Could not open help topics file NULL
       

  This problem is usually caused by installing AMIDE in /usr/local instead of /usr. Current versions of the GNOME help browser only check in /usr/share/gnome/help for application help files. To fix this, you can either install AMIDE in /usr, or you can link the AMIDE help files in /usr/local/share/gnome/help to /usr/share/gnome/help with the following command (done as root):

         ln -s /usr/local/share/gnome/help/amide /usr/share/gnome/help/amide
       

Compilation Errors

• I've installed AMIDE from source, but it doesn't seem to have support for XMedCon/GSL/DCMTK/etc. when I run the program.

  First, double check that you've actually got the package in question installed on your computer. Second, check what the error messages where when you ran "./configure"; some helpful stuff will be print out by configure itself, and more useful information will be in the config.log file.

  The most common problems on Linux are:

  1. xmedcon-config and/or gsl-config are not in your PATH statement. Find where these executables are, and add them to your path. The following line will usually do the trick:

     export PATH=$PATH:/usr/local/bin:/usr/local/xmedcon/bin 

     Then rerun the configure script.

  2. Your system does not know the location of the libraries for the packages in question. Find where the libraries are, and add these directories to /etc/ld.so.conf. The directories you'll need to add are usually "/usr/local/xmedcon/lib" and "/usr/local/lib". Then run (as root) /sbin/ldconfig, and rerun the configure script.

Running Errors

• When I start AMIDE, there is an error of "libmdc.so.1 cannot open shared object file: No such file or directory". Or alternatively libvolpack.so.1 may be the problem.

  This is most likely because the system doesn't know where to find this library. Check where the library is, and that the directory where the library residues is entered in /etc/ld.so.conf. If its not, you'll need to add the location to /etc/ld.so.conf, and run /sbin/ldconfig to tell it about the changes in ld.so.conf.