HOWTO setup a professional design environment for gEDA
Peter Kaiser, firstname.lastname@example.org
This document is released under GFDL
24. January 2005
Who should read this document
After you have successfully installed gEDA software on your computer, you might want to start immediately working. Do so, if you are a hacker. You will have fun and come to good results.
But if you have requirements like:
Several people work on the same design. May be one person draws the symbols, the next one creates the schematic and does simulation and a third one is responsible for the layout.
Someday, somebody else will take your design and needs to make changes.
Regular automatic backups
Then a design environment with scripts and different libraries is needed. This HOWTO describes the way to set it up and gives examples to make it easy for you.
At least one symbol, necessary for a design, is not in the standard library. That's the reason why you will have more directories, containing symbols for your design. We can distinguish between four different kind of libraries:
System library: This library comes with gschem distribution. It's located in <geda-install>/share/gEDA/sym. It contains hundred of symbols and is the first choice for new users.
Technology library: All users in a network have access to this library. In a semiconductor design, this is the vendor symbol library for a specific technology.
User library: This library is somewhere in your home directory and contains your private symbols. I suggest ~/gEDA.
Project library: This contains symbols for a single project. A typical example is a block symbol in a hierarchical design. I suggest to create a ./sym directory in the project directory.
To get access from gschem to the libraries, you need to tell the program during the startup, where it can find those libraries. Most of the gaf tools read in 6 setup files. The first three are for the common setup and read by most programs (gschem, gnetlist, gattrib, .. ). The second three are program specific. Each triple has the following order: System, user and project rc file. This results in the following order:
* This is valid for the next versions after 20041228
The scripting language for the setup files is guile, which is a special version of scheme. If you want to write your own scripts and become a guru, you can get more information from:
The Scheme Programming Language; R. Kent Dybvig; The MIT Press, Cambridge Massachusetts; ISBN 0-262-54148-3
Useful commands in a rc file
Comments do start with “;;”
Display messages to the console window:
(display "gschemrc: loading private design environment \n")
Add a new library:
Underlying schematics for hierarchical designs:
Copy all invisible attributes from the symbol library to the schematic:
Running different versions as the same user
I always use prefix during the installation. The stable version is in:
the CVS version is in:
I switch between both with the PATH and LD_LIBRARY_PATH variable in
< tbd >
< tbd >
Example user gafrc file
(display "gafrc: \n")
(display "gafrc: loading DH0MAY design environment \n")
(display "gafrc: \n")
;; User symbol libraries
;; Project symbol librariy
;; Hierarchical designs, symbols
;; Hierarchical designs, underlying schematics
Document Revision History
07. January 2005
Comments and suggestions about this document are welcome. Please send me an email.