demos.README, Release 3.0, July 2, 2007 This is the third release of pcblander demos. To get started, put all files in the above "bin" directory into your search path and download the demos into your work area. The demo files build pcb landpatterns. To build a landpattern, type "pcblander ", where you supply the name of from one of the source files in this demo directory. Note: the bin/pcblander.pp file has changed for this release - be sure to download it before attempting to build *.sfp files. If you are not sure of the revision of your files, type "pcblander -V". landgen.pl should be at revision 0.1.3 or greater. Here's a quick summary of the files in the demo area 0603.lander, DIP_14.lander, FBGA256.lander, MOLEX_71661_2068.lander, SO_14.lander, TQFP48.lander These are source files for generating landpatterns. They are not as compact as the files using macros, but they illustrate the basic building constructs of pcblander. template.lander This is a generic source file for generating a landpattern. Use this as a starting point for generating custom landpatterns. It has lots of hints for generating landpatterns other than those shown in the demos. ## new for Release 2.0 ## footprints.lander This is a source file that builds a mega-landpattern. It illustrates the use of macros and of placing landpattern elements within a landpattern. You can view a pdf of it's output in footprints.pdf footprints.pdf A pdf file of the landpattern generated by running: "pcblander footprints.lander". ## new for Release 3.0 ## 0603.sfp, 1206.sfp, SIP_4.sfp, DIP_14.sfp, TQFP48.sfp These are source-footprint files, as they contain both the source code for generating a footprint and the footprint itself. They can be used as-is to both generate a footprint or as a footprint. They are a compact and foolproof (? well maybe hard to fool) way of keeping footprints and their more human readable definitions in-sync, as the footprint and source code are in the same file. If you wish to modify an sfp file's footprint, edit the code in the top block (prefaced by #@teaser|'s). Then type the footprint name at the command line, and it will rebuild itself to look like what you have edited. What is going on behind the scenes is the pcblander program interprets each line with a "#@teaser|" string and "exit()"s before it sees the footprint code. The pcb program ignores the lines that start with a "#" and interprets only the other lines. In this manner, both pcblander and pcb footprint code can co-exist in same file without interfering with each other. footprints.inc The file defines the BGA(), DIP(), SIP(), QFP(), amd SO() landpattern macros used in Releases 2 and 3 of the demo files. These make defining standardized packages much simpler, as only a few parameters need to be specified (and the rest are known from the type of package the macro is building). landutils.inc Some macros for helping with landpattern generation. Macros exist for generating pad columns, pad rows, a "1" in silkscreen, a "+" in silkscreen, brackets in silkscreen. constraints.inc This is a set of constraints used by all the landpatterns. Rather than hard code attributes that are common for all landpatterns, they are coded once and placed in this file. Anything that can be typed into a landpattern source file can be put in the constraints file. If you don't wish to include this file, copy it's contents into the top of your landpattern source file and remove the "include" directive.