gEDA-cvs: CVS update: gschem.tex

[cvspsrv@xxxxxxxx]

  User: ahvezda 
  Date: 05/03/14 22:54:27

  Modified:    .        gschem.tex
  Log:
  Last minute README updates.  Updated version in toplevel Makefile.  make
  
  dist updates to .po files.
  
  
  
  
  Revision  Changes    Path
  1.2       +10 -13    eda/geda/devel/docs/gschem/gschem.tex
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: gschem.tex
  ===================================================================
  RCS file: /home/cvspsrv/cvsroot/eda/geda/devel/docs/gschem/gschem.tex,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -b -r1.1 -r1.2
  --- gschem.tex	28 Sep 2003 00:44:06 -0000	1.1
  +++ gschem.tex	15 Mar 2005 03:54:26 -0000	1.2
  @@ -1,4 +1,4 @@
  -% $Id: gschem.tex,v 1.1 2003/09/28 00:44:06 ahvezda Exp $
  +% $Id: gschem.tex,v 1.2 2005/03/15 03:54:26 ahvezda Exp $
   %
   % gEDA - GPL Electronic Design Automation
   % Copyright (C) 2003 Ales Hvezda
  @@ -80,22 +80,19 @@
   installed the tools correctly by running the following commands:
   \begin{verbatim}
   
  -        libgeda-config --version
  -        gesym-config --version
           which gschem
           ldd `which gschem`
   
   \end{verbatim}
  -The first two should return the version of the installed tools
  -(libgeda and the symbol library) and the next command should return
  -the path to the {\tt gschem} binary.    The final command (only on
  -unix-like operating systems which include the {\tt ldd} utility for
  -listing dynamic dependencies of executibles or shared objects)
  -will return which libraries are linked to {\tt gschem}; all of the
  -request libraries must be found for {\tt gschem} to run.  If these commands
  -do not return the expected results, then most likely the gEDA tools are
  -not installed properly.  Please see the appropriate INSTALL docs (which
  -came with the distribution) for more info on installing the gEDA tools.
  +The first command should return the path to the {\tt gschem} binary and the
  +second command (only on unix-like operating systems which include the {\tt
  +ldd} utility for listing dynamic dependencies of executibles or shared
  +objects) will return which libraries are linked to {\tt gschem}; all of
  +the request libraries must be found for {\tt gschem} to run.  If these
  +commands do not return the expected results, then most likely the gEDA
  +tools are not installed properly.  Please see the appropriate INSTALL
  +docs (which came with the distribution) for more info on installing the
  +gEDA tools.
   
   
   To run gschem execute ``{\tt gschem}'' at any shell prompt (without