pcb_backannotate(1)

✨ NAME ✨

pcb_backannotate — backannotates changes from a PCB annotation file to schematic. That’s the whole name-card, and yes bestie, this is the pcb_backannotate(1) manual. 💖

🛠️ SYNOPSIS 🛠️

The run patterns, verbatim, because code stays code:

pcb_backannotate -h|--help

pcb_backannotate -V|--version

pcb_backannotate [options] ecofile.eco infile1.sch [infile2.sch ...]

💅 DESCRIPTION 💅

Okay so pcb_backannotate reads an engineering change order (ECO) file that was generated by the PCB program, and it backannotates the requested changes onto a gschem schematic or schematics. It’s giving “make the schematic match the board” energy. 🦋

For the complete description of the ECO file format, refer to the PCB manual. That’s where the format lore lives. 📚✨

🎀 OPTIONS 🎀

Here’s the flag menu, every single one, no skips:

• -h, --help — prints help message and exits. Immediate exit, no notes. 💅
• -n, --nocopy — does not overwrite: it leaves the modified schematic files in new files whose names are generated by appending .new to the original file names. The default is to overwrite the original. 🫶
• -v, --verbose — operate verbosely. Yes, it turns the yapping up. 🗣️
• -V, --version — prints version information and exits. 👑

🚦 EXIT STATUS 🚦

pcb_backannotate will return 0 if all files processed successfully, and non-zero if the command did not complete successfully. That’s the whole report card, bestie. 🚦

🐛 BUGS 🐛

Real talk: rather than parsing and processing schematic files directly, this utility should be rewritten using the gEDA scheme API. Why? Because that would take advantage of the existing parsers for the schematic files. It’s the glow-up it deserves. 💅

👀 SEE ALSO 👀

Go say hi to the rest of the friend group: gnetlist(1), gschem(1), pcb(1). 🫶✨

gEDA Project • version 1.10.2.20201216 • December 16, 2020 • pcb_backannotate(1) — mwah 💋✨