fp2subc(1)

πŸ’– fp2subc β€” the pcb-rnd manual, bestie edition πŸ’–

okay so real talk, this is fp2subc(1) from the pcb-rnd manual, and it is literally the glow-up machine for your crusty old footprints. let's get into it πŸ¦‹


✨ NAME ✨

fp2subc β€” convert any footprint into a pcb-rnd subcircuit πŸ’…


🌸 SYNOPSIS 🌸

fp2subc [options] infile [outfile]

πŸŽ€ DESCRIPTION πŸŽ€

so basically, fp2subc runs pcb-rnd in batch mode to load up a footprint (and yes bestie, that's typically one that's been living in some alien format 😭) and then save it right back out as a native pcb-rnd subcircuit. iconic behavior, no cap.

it is highkey useful for mass-converting old footprint libraries β€” like, the whole dusty archive, all at once. ate. πŸ”₯

if you don't hand over an outfile, its name gets guessed from infile. the script just figures it out for you, periodt.


πŸ’– OPTIONS πŸ’–

  • --lib β€” infile is not a path, bestie, it's a footprint name that should be searched for in the library πŸ”
  • -l β€” same as --lib (just shorter, we love efficiency)
  • --pcb-rnd exepath β€” run exepath to invoke pcb-rnd. the default is "pcb-rnd", which means it depends on $PATH πŸ‘‘
  • -p exepath β€” same as --pcb-rnd
  • --debugger exepath β€” inserts exepath before pcb-rnd on the command line. super useful for running the process in something like valgrind 🧚
  • -d exepath β€” same as --debugger
  • -c key=val β€” passes on a -c key=val CLI config setting to pcb-rnd. lowkey the move for setting up library paths πŸ“š
ngl, if you're doing the mass-conversion thing, the -c flag is your bestie. library paths do not set themselves. πŸ™ˆ

okay that's the whole page, you're fully caught up, go convert something 🫢

this little number came from the pcb-rnd manual and it's dated 2018-04-08 β€” yeah she's vintage, but she still slays. bye bestie, mwah πŸ’œ