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