This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
geda:faq-gnetlist [2012/02/20 15:14] 127.0.0.1 external edit |
geda:faq-gnetlist [2014/04/18 08:15] (current) vzh Add links to translations |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | //Translations of this page are also available in the following languages:// [[faq-gnetlist.fr|Français]], [[faq-gnetlist.ru|Русский]]. | ||
+ | |||
====== Gnetlist ====== | ====== Gnetlist ====== | ||
Line 6: | Line 8: | ||
====== Bill of Materials (BOM) Generation ====== | ====== Bill of Materials (BOM) Generation ====== | ||
- | There are five different backends for [[http://geda.seul.org/tools/gnetlist/index.html|gnetlist]] which enable you to export a BOM. Call them with -g and be sure to give the output file name with the -o option: | + | There are five different backends for gnetlist which enable you to export a BOM. Call them with -g and be sure to give the output file name with the -o option: |
<code> | <code> | ||
- | gnetlist -g partslist3 -o output.bom schematic.sch | + | gnetlist -g partslist3 -o output.bom schematic.sch |
- | </code> | + | </code> |
- | gnetlist descends into sub sheets and list the contents of these schematics along with the parts from the top document. | + | gnetlist descends into sub sheets and list the contents of these schematics along with the parts from the top document. |
The backends bom and bom2 require read access to a local file called attribs. This file should contain the name of the attributes to be listed each in a seperate line. E.g: | The backends bom and bom2 require read access to a local file called attribs. This file should contain the name of the attributes to be listed each in a seperate line. E.g: | ||
Line 25: | Line 27: | ||
The bom backend needs to read an attribs file (see above). The list produced by "-g bom" will contain as many lines as there are components. Columns are seperated by tab characters. Lines are not sorted. | The bom backend needs to read an attribs file (see above). The list produced by "-g bom" will contain as many lines as there are components. Columns are seperated by tab characters. Lines are not sorted. | ||
- | === bom2 === | + | === bom2 === |
The bom2 backend also needs to read an attribs file. With "-g bom2" the refdeses of all components with the same value will be collected into a single line. Columns are seperated by colons. Different items in the same column are seperated by a komma character. | The bom2 backend also needs to read an attribs file. With "-g bom2" the refdeses of all components with the same value will be collected into a single line. Columns are seperated by colons. Different items in the same column are seperated by a komma character. | ||
Line 132: | Line 134: | ||
then you need to create a file called “attribs” in the current directory which contains the attributes which you want inside the bom file. An example of this file would be: | then you need to create a file called “attribs” in the current directory which contains the attributes which you want inside the bom file. An example of this file would be: | ||
- | <xterm>device | + | <code>device |
- | value</xterm> | + | value</code> |
For information about BOM generation see [[#Bill of Materials (BOM) Generation|above]]. | For information about BOM generation see [[#Bill of Materials (BOM) Generation|above]]. | ||
Line 159: | Line 161: | ||
{{:geda:ambiguous1_fixed.png}} | {{:geda:ambiguous1_fixed.png}} | ||
+ |