docs/wiki/geda-olib_readme.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   2  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   3 <html>
   4 <head>
   5   <title></title>
   6   <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
   7   <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
   8   <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
   9
  10   <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
  11 </head>
  12 <body>
  13
  14
  15 <h1 class="sectionedit451"><a name="olib_orcad_tm_converter_readme" id="olib_orcad_tm_converter_readme">olib (OrCAD (TM) converter) README</a></h1>
  16 <div class="level1">
  17 <pre class="code">###############################################################
  18 README and release notes for olib2geda - 1 settembre 2002
  19 OrCAD (TM) lib ASCII dump to gEDA .sym converter
  20 ###############################################################
  21
  22
  23 What it olib2geda?
  24 It&#039;s a simple automated converter from OrCAD v4 (in SDT version 1.10) parts
  25 library (in ASCII dump format, through &quot;decomp&quot; utility) to gEDA component
  26 definition in .sym format file.
  27 It allow an initial dumb conversion file to file, with one lib converted in
  28 multiple .sym file, one per component in library.
  29 The converted component file needs little editing to become usable, but in some
  30 case needs no editing at all.
  31
  32
  33 What olib do.
  34 * Convert box shaped component in OrCAD (TM) lib in .sym file in gEDA format
  35 * Place pin, pin name, pin type, pin number
  36 * Place logic bubble when needed (DOT attribute in OrCAD (TM), for logic nega-
  37     tion)
  38 * Place clock arrow when needed (CLK attribute)
  39 * Place reference, from REFERENCE statement in OrCAD (TM)
  40 * Place Part name as label and device name as attribute
  41 * Parse and draw non-box component, with LINE, ARC, CIRCLE and TEXT
  42 * Add power pin as invisible net=name:pin attribute when detected (in OrCAD (TM)
  43     invisible pin has tipically T0 and B0 coords)
  44 * Through command line switch, hides pin name in VECTOR drawed symbols, allowing
  45     better appearance
  46 * Write both new (20020825) and old (20020209) file format for .sym files
  47     through a switch on the command line
  48
  49
  50 What olib do not.
  51 * Do not parse and store alternate component drawing (statement CONVERT in
  52     OrCAD (TM))
  53 * Do not handle drawing part using VECTOR list from another part (statement
  54     VECTOR &#039;partname&#039; in OrCAD (TM))
  55 * Do not handle FILL statement in VECTOR statement (incompatible with gEDA, but
  56     for what i know is used only for &quot;better&quot; part drawing)
  57 * Do not handle multiple part in one package (slots in gEDA)
  58
  59
  60 Bugs.
  61 More and more. But for the use that I do bugs aren&#039;t so critical.
  62 If you find a bug or want improvements to the program, feel free to contact me
  63 at the e-mail address at the end of this text.
  64
  65
  66 How to obtain last version.
  67 Open the URL:
  68 http://digilander.libero.it/tailchaser
  69 in section &quot;Linux&quot; you can see the main page of olib.
  70
  71
  72 Compile and install.
  73 [[ Ales here, I have incorperated olib into the ./configure build mechanism,
  74    so these instructions only apply if you build from Mario&#039;s distribution ]]
  75
  76 To compile program go in directory &#039;src&#039; of the unpacked tarball, and type
  77 &#039;make&#039;. This produces the binary executable, named &#039;olib&#039;.
  78 Compilation process uses the flex scanner generator to generate the file
  79 &#039;olib.c&#039; from the &#039;olib.lex&#039;, and link the library math to the code. The binary
  80 included in the distribution is compiled on a P266-MMX with RedHat 7.2, with gcc
  81 version 2.96 and flex 2.5.4, but the program don&#039;t require any special feature
  82 or critical function, as far as I know. At the end of compilation phase, you can
  83 see two warnings:
  84 * warning, -s option given but default rule can be matched
  85 * warning: `yyunput&#039; defined but not used
  86 this is normal, don&#039;t affect program functionality, and you can safely ignore
  87 it.
  88 Installation is not needed for normal operations, but if you want you can copy
  89 only the executable (olib) on a directory in the PATH.
  90
  91
  92 Use of olib.
  93 To convert library, first convert it to ASCII dump with &#039;decomp&#039; utility
  94 included in the OrCAD (TM) distribution. After that invoke the lib converter:
  95 olib path/to/file/file_ascii prefix where &#039;prefix&#039; is used to generate file name
  96 of every symbol, like:
  97 prefix-partname-1.sym
  98 During the process, you can see a lot of ugly text scrolling in the terminal,
  99 that show the progress of the conversion. If you want to read this text, you can
 100 redirect the stderr output to a file:
 101 olib path/to/file/file_ascii prefix 2&gt; logfile.txt
 102 where &#039;2&gt;&#039; instruct the shell to redirect stderr output to logfile.txt.
 103 The converter write one file per part, in the current directory. At the end of
 104 the execution you can see a lot of file in the directory, extracted from OrCAD
 105 library.
 106 In the (not so improbable) case of incomplete conversion of a part (i.e. because
 107 of unsupported VECTOR &#039;partname&#039; statement), the file of the incomplete part
 108 will be named &#039;prefix-partname-1.sym.part&#039;, stand for partial conversion.
 109 If the conversion process stops with the message: &quot;flex scanner jammed&quot;, the
 110 converter has encountered an unknown statement, an incompatible version of
 111 library, or a bug. If you can, please report the complete log and the library
 112 dump, to allow corrections or improvements.
 113
 114
 115 Mario Pascucci
 116 &lt;m.pas@libero.it&gt;</pre>
 117
 118 </div>
 119 </body>
 120 </html>