Migrating to geda pcb - getting started learning guide?

[wb0gaz]

Hello - I wish to find some basic "getting started" training, documentation, guide or examples to help me migrate to geda pcb (from another software environment that has been obsoleted by its author).  I am familiar (enough) with PC layout (I go direct-to-layout, without using auto-routing, because my projects are usually analog/RF in nature), so I am trying to ease the migration to geda pcb.

Are there such resources?

Thank you

[wilfred]

You're going to get recommendations for everyone elses favourite package. You might as well reveal if you want a free and open source choice or a commercial option.

You have doubtless done a search on "getting started with geda" in you favourite search engine. Which is why I'd be tempted to consider Kicad. There's a lot more info available.

[nctnico]

Hello - I wish to find some basic "getting started" training, documentation, guide or examples to help me migrate to geda pcb (from another software environment that has been obsoleted by its author).  I am familiar (enough) with PC layout (I go direct-to-layout, without using auto-routing, because my projects are usually analog/RF in nature), so I am trying to ease the migration to geda pcb.

Are there such resources?

Thank you

IIRC there is enough on the Geda pages themselves to get started with a design. Be sure to look at pcb-rnd too because it seems to get a lot of active development lately. Still I wonder why you'd want to move away from a working package. What kind of features are you looking for?

[wb0gaz]

Thank you.

In a nutshell, I need to place components, lines, rectangles/circles/shapes, cutouts/boundaries, holes, vias, etc., on top/bottom layers, be able to group and move them as needed, then take the resulting layout and generate a Gerber file.

I do not want to generate a schematic and have the software route for me, as I focus on RF/analog design where layout is often more detailed than the corresponding schematic.

[ScribblesOnNapkins]

pcb-rnd doesn't require you to use any particular auto routing if you use a schematic or netlist as input. That info is really only used to make sure you don't short between nets or violate the DRC rules you set. Typically this happens when you route things too close for your fabs rules.

If you want to have a trace going to a pin that says N.C. on the netlist and run it in a ring around the board for no reason, you can do that.
If you want to short two nets on the layout in one fixed point to make a connection between your digital and analog ground you can.
etc, etc.
It should let you do what you want, not what we as it's creators think you need.