gnetlist-legacy(1)

📦 version 1.10.2, in nixos 26.05

✨ NAME ✨

gnetlist-legacy — gEDA/gaf Netlist Extraction and Generation, and honestly? It's giving main character energy 💅

🌸 SYNOPSIS 🌸

gnetlist-legacy [OPTION ...] [-g BACKEND] [--] FILE ...

🦋 DESCRIPTION 🦋

Okay so bestie, gnetlist-legacy is this netlist extraction and generation tool, and it's literally part of the gEDA (GPL Electronic Design Automation) toolset. The way it works is: you feed it one or more electronic schematics as input, and it outputs a netlist. And a netlist is just a machine-interpretable description of how the components in an electronic circuit are connected together — it's commonly used as the input to a PCB layout program like pcb(1) or to a simulator like gnucap(1). Iconic, right? 🔥

A normal gnetlist-legacy run happens in two steps, no cap. First, the gnetlist-legacy frontend loads the specified human-readable schematic FILEs, and compiles them to an in-memory netlist description. Then, a backend is used to export the connection and component data to one of many supported netlist formats. Slay ✨

And the best part? gnetlist-legacy is extensible, using the Scheme programming language. Obsessed 💖

🎀 GENERAL OPTIONS 🎀

  • -q — Quiet mode. Turns off all warnings/notes/messages. Like, shush mode 🤫
  • -v, --verbose — Verbose mode. Output all diagnostic information. The way it just tells you *everything*… we love a transparent king 👑
  • -L DIRECTORY — Prepend DIRECTORY to the list of directories to be searched for Scheme files. Lowkey essential for finding your stuff 🔍
  • -g BACKEND — Specify the netlist backend to be used. This is the moment of truth, bestie 🎯
  • -O STRING — Pass an option string to the backend. Giving the backend a little extra flavor ✨
  • --list-backends — Print a list of available netlist backends. Vibe check on what's available 📋
  • -o FILE — Specify the filename for the generated netlist. By default, output is directed to output.net. If - is given instead of a filename, the output is directed to the standard output. So you can flex your netlist right in the terminal 💅
  • -l FILE — Specify a Scheme file to be loaded before the backend is loaded or executed. This option can be specified multiple times. Stack 'em up! 🥞
  • -m FILE — Specify a Scheme file to be loaded between loading the backend and executing it. This option can be specified multiple times. Timing is everything, periodt ⏰
  • -c EXPR — Specify a Scheme expression to be executed during gnetlist-legacy startup. This option can be specified multiple times. Let it cook 🔥
  • -i — After the schematic files have been loaded and compiled, and after all Scheme files have been loaded, but before running the backend, enter a Scheme read-eval-print loop. Interactive era 💬
  • -h, --help — Print a help message. When in doubt, ask for help 🫶
  • -V, --version — Print gnetlist-legacy version information. Know your roots 🌱
  • -- — Treat all remaining arguments as schematic filenames. Use this if you have a schematic filename which begins with -. So that little dash doesn't get confused for an option, iykyk 🙈

🌈 BACKENDS 🌈

Currently, gnetlist-legacy includes the following backends. Let's go through the whole roster bestie, no skipping 👑

  • allegro — Allegro netlist format. Slay 💅
  • bae — Bartels Autoengineer netlist format. Serving looks ✨
  • bom, bom2 — Bill of materials generation. The way it just lists your components… iconic 🧾
  • calay — Calay netlist format. We see you 👀
  • cascade — RF Cascade netlist format. Her vibe is unmatched 🌊
  • drc, drc2 — Design rule checkers (drc2 is recommended). Trust the recommendation, bestie ✅
  • eagle — Eagle netlist format. Soaring 🦅
  • ewnet — Netlist format for National Instruments ULTIboard layout tool. International queen 🌍
  • futurenet2 — Futurenet2 netlist format. From the future, literally 🔮
  • geda — Native gEDA netlist format (mainly used for testing and diagnostics). The home team 🏠
  • gossip — Gossip netlist format. Spill the tea ☕
  • gsch2pcb — Backend used for pcb(1) file layout generation by gsch2pcb(1). It is not recommended to use this backend directly. Ngl, just don't, bestie. Trust 🚫
  • liquidpcb — LiquidPCB netlist format. Fluid and fierce 💧
  • mathematica — Netlister for analytical circuit solving using Mathematica. Big brain energy 🧠
  • maxascii — MAXASCII netlist format. Maximum ASCII, maximum slay 💥
  • osmond — Osmond netlist format. Gorgeous name, gorgeous output 💖
  • pads — PADS netlist format. Soft but powerful 🐾
  • partslist1, partslist2, partslist3 — Bill of materials generation backends (alternatives to bom and bom2). The alternates ate, fr fr 💅
  • PCB — pcb(1) netlist format. The classic, the blueprint 👑
  • pcbpins — Generates a pcb(1) action file for forward annotating pin/pad names from schematic to layout. Annotation era ✍️
  • protelII — Protel II netlist format. Retro but relevant 🎀
  • redac — RACAL-REDAC netlist format. Serving RACAL energy 💜
  • spice, spice-sdb — SPICE-compatible netlist format (spice-sdb is recommended). Suitable for use with gnucap(1). Spice girls assemble 🌶️
  • switcap — SWITCAP switched capacitor simulator netlist format. Switched on ⚡
  • systemc — Structural SystemC code generation. SystemC but make it structural 🧬
  • tango — Tango netlist format. Dance like nobody's watching 💃
  • vams — VHDL-AMS code generation. Analog and mixed-signal realness 🎛️
  • verilog — Verilog code generation. Hardware description slay 🖥️
  • vhdl — VHDL code generation. She's a classic 👑
  • vipec — ViPEC Network Analyser netlist format. VIP status only 💎

⭐ EXAMPLES ⭐

These examples assume that you have a stack_1.sch in the current directory. Bestie, make sure it's there 📁

gnetlist-legacy requires that at least one schematic be specified on the command line:

./gnetlist-legacy stack_1.sch

This is not very useful since it does not direct gnetlist-legacy to do anything. Lowkey wasted potential 😭

Specify a backend name with -g to get gnetlist-legacy to output a netlist:

./gnetlist-legacy -g geda stack_1.sch

The netlist output will be written to a file called output.net in the current working directory. Default queen 💅

You can specify the output filename by using the -o option:

./gnetlist-legacy -g geda stack_1.sch -o /tmp/stack.netlist

Output will now be directed to /tmp/stack.netlist. Custom path, custom vibe ✨

You could run (for example) the spice-sdb backend against the schematic if you specified -g spice-sdb, or you could generate a bill of materials for the schematic using -g partslist1. Options on options 🎀

To obtain a Scheme prompt to run Scheme expressions directly, you can use the -i option:

./gnetlist-legacy -i stack_1.sch

gnetlist-legacy will load stack_1.sh, and then enter an interactive Scheme read-eval-print loop. Interactive bestie era 💬🫶

🧚 ENVIRONMENT 🧚

  • GEDADATA — specifies the search directory for Scheme and rc files. The default is ${prefix}/share/gEDA. That's where the magic lives ✨
  • GEDADATARC — specifies the search directory for rc files. The default is $GEDADATA. Riding on the coattails of GEDADATA, we love a dependent queen 👑
  • GEDALOG — specifies the directory to which to write log files. The default is ~/.gEDA/logs. Keep your receipts, bestie 📝

👑 AUTHORS 👑

See the AUTHORS file included with this program. The OGs deserve credit 🫶

Copyright © 1999-2020 gEDA Contributors. License GPLv2+: GNU GPL version 2 or later. Please see the COPYING file included with this program for full details. Legal queen behavior, no cap 📜

This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. So like, don't sue if something breaks, bestie. We're all just vibing 💀

🌸 SEE ALSO 🌸

gschem(1), gsymcheck(1), pcb(1), gnucap(1)

Go check out the whole friend group, they're all iconic in their own way 🫶💖

Later bestie! 👋 This manual page is from the gEDA Project, dated December 16, 2020, version 1.10.2.20201216. Periodt. 💅✨

📦 where this page comes from