The easiest way to install the gEDA Suite is to grab the gEDA Suite CD ROM and use it. The instructions are contained in the README available on the downloads page. Note that the CD ROM installer assumes that you are running the Gnome desktop! The same is true of the gEDA tools: They use the GTK widget set which underlies Gnome. If you are running KDE, you need to at least get the Gnome libraries installed on your machine before trying to run the installer.
The gEDA Suite CD holds the tarballs of more than one dozen popular gEDA applications. It also incorporates a GUI-based install wizard which checks your system configuration, asks you a few questions, and then oversees the compilation and installation of the different gEDA applications. The install wizard just automates the normal “./configure && make && make install” process used to build GNU software from source. Therefore, it is more or less platform independent (as long as you are running Linux).
In the event that the install wizard can’t automatically install the gEDA Suite, you can still get the source tarballs off the CD and build them manually. The instructions are available from the download web page, as well as in the INSTALL file on the CD.
Also, people have created RedHat RPMs, Debian Debs, and Mac OSX Fink packages if you prefer to install that way. These binary distributions are available on the downloads page. Finally, source tarballs for all programs are also available on the downloads page.
By the way, it’s always a good idea to install gEDA into its own directory. That way, when you want to upgrade the package you just need to delete the directory and re-install. (This advice is true for any large suite of applications in unix.) More on this below.
Finally, if the instructions here aren’t enough, David Hart has placed a useful and detailed guide for configuring and installing gEDA (for Fedora Core 4, but probably helpful with other distros too), as well as a gEDA Tutorial for new users.
As of this writing, no advanced method to uninstall the gEDA Suite exists. Unlike a certain commercial operating system, Linux (and unix) were not designed with the goal of easy package management in mind, and we all suffer with this legacy.
Therefore, we recommend that you install the gEDA Suite into its own special directory. For example, the CD Installer will place the Suite’s executables into ${HOME}/geda-install
by default. Then, if you need to uninistall the gEDA Suite, you can just delete the entire directory.
(More advanced methods to install/uninstall packages on Linux/unix also exist. Could somebody please write about them here?)
Different applications belonging to gEDA/gaf all use the same shared library, libgeda.so. Things in the library change from one gEDA release to another. Therefore, applications are prevented from linking to libgeda.so if their release codes don’t match.
If you need to upgrade one application in gEDA/gaf, you will need to first uninstall your old version, and then install an entirely new set of applications, including the library and all components of gEDA/gaf.
Alternately, you can install the new gEDA/gaf into a new directory, and then edit your ${PATH}
, ${PKG_CONFIG_PATH}
, and ${LD_LIBRARY_PATH}
environment variables to remove the old directory, and point to the new one. Make sure you do this before you try installing the new gEDA/gaf.
Amazingly enough, some people simply copy the installer .iso file using “cp” onto a blank CD, and then try to use it. This won’t work. You need to “burn” a CD with the .iso in a way which writes the whole filesystem directly onto the CDROM. The linux/unix command to do this is usually “cdrecord”, or perhaps a GUI derivative of this utility. Don’t just “cp” the .iso file onto a blank CD!
Many modern Linux distributions will not automatically run executables on installed media. This is a security precaution. To overcome this, you need to mount the CD in a way which grants permission for executables to run. For example, in Gentoo and Debian you should mount the CD ROM this way:
mount -o exec -t iso9660 /dev/cdrom /mnt/cdrom
The detailed flag or mount point relevant to your distribution might be a little different; read the manual for mount (”man mount”) if you have any questions about how to do this.
After you have mounted the CD with execute permission, you can then run the installer from the command line like this:
/mnt/cdrom/installer
At this point, the install wizard’s GUI should pop up, and you can get to installing. If you can’t install, please try doing an “ls” of the CD to see if it is readable. That is, do this:
ls -l /mnt/cdrom/
And verify that you get a directory listing instead of an error message (or nothing at all).
First off, please keep in mind that the CD ROM’s installer only works on Linux. The CD ROM installer will not work on Sun, BSD, or Mac OSX, and it certainly won’t work on Windows.
As a general rule, if you are having problems installing gEDA from the CD, here are the things you can try:
–log
flag set, it will place a file called Install.log into your local directory (where you are running the installer). This file is a log of all commands issued and all responses generated during the install process. It allows you to save the data displayed on the log window displayed during the install process. Running the installer with –log
set is a good idea if you are experiencing problems; you can send your Install.log file to an expert who might be able to diagnose your problem. More on this later.After you install the gEDA Suite off the CD ROM, make sure you do the following:
${PATH}
to point to the location where your new gEDA executables live (for example, /home/your-name/geda-install/bin
). Make sure that you remove pointers to old gEDA editions, if they exist. You should not only set the ${PATH}
in your current shell, but you should also set it in your shell config scripts (i.e. .bashrc or .cshrc)${LD_LIBRARY_PATH}
to point to the location where your new gEDA executables live (for example, /home/your-name/geda-install/lib
). Make sure to remove pointers to old gEDA editions, if they exist. You should not only set the ${LD_LIBRARY_PATH}
in your current shell, but you should also set it in your shell config scripts (i.e. .bashrc or .cshrc)