geda:faq-gschem
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
geda:faq-gschem [2014/04/25 12:53] vzh Remove unnecessary spaces |
geda:faq-gschem [2015/07/06 16:53] (current) vzh Added a link to new page about generators. |
||
|---|---|---|---|
| Line 205: | Line 205: | ||
| Additionally, there is a tool (ibs2symdef.py) for generating symdef files for use with djboxsym from IBIS models. It is distributed with the PyBIS project: [[https://github.com/russdill/pybis/wiki|PyBIS wiki]] | Additionally, there is a tool (ibs2symdef.py) for generating symdef files for use with djboxsym from IBIS models. It is distributed with the PyBIS project: [[https://github.com/russdill/pybis/wiki|PyBIS wiki]] | ||
| + | |||
| + | Check the [[gschem symbol generators]] page for others generators | ||
| + | available. | ||
| ===== Where can I find information on gschem's file format? ===== | ===== Where can I find information on gschem's file format? ===== | ||
| Line 239: | Line 242: | ||
| * The key is: start gschem in the same directory as where your gafrc lives. | * The key is: start gschem in the same directory as where your gafrc lives. | ||
| - | ===== Can gafrc use a variable to set the root of my library? ===== | + | ===== How can I set the root of my library? ===== |
| - | Currently (v1.3.1) gschem does not descend into subdirectories of the symbol library. You have to give individually each and every directory of your local lib in your gafrc file. However, you don't have to repeat the absolute base path over and over. You can use the function 'build-path' to concatenate the path on the fly: | + | There are two approaches. If you want each of your library to have a unique name, you have to set it individually for each and every directory of your local lib in your gafrc file. However, you don't have to repeat the absolute base path over and over. You can use the function 'build-path' to concatenate the path on the fly: |
| <code>(define gedasymbols "/path/to/local/library") | <code>(define gedasymbols "/path/to/local/library") | ||
| (component-library (build-path gedasymbols "analog")) | (component-library (build-path gedasymbols "analog")) | ||
| (component-library (build-path gedasymbols "block")) | (component-library (build-path gedasymbols "block")) | ||
| (component-library (build-path gedasymbols "connector"))</code> | (component-library (build-path gedasymbols "connector"))</code> | ||
| + | |||
| + | If you don't want to list separate subdirectories, you can only | ||
| + | set the name of a root directory using: | ||
| + | <code>(component-library-search "/path/to/local/library" "library:")</code> | ||
| ===== Can the library path contain environment variables? ===== | ===== Can the library path contain environment variables? ===== | ||
| Line 278: | Line 285: | ||
| (component-library "/bar/foo/localgedalib2") | (component-library "/bar/foo/localgedalib2") | ||
| </code> | </code> | ||
| - | You have to add each and every dir of your local library. Subdirs are not automatically recognized by gschem and gsch2pcb. Its a good idea to place this gafrc in your projects dir. That way, if you start gschem from some other place, you still get the system symbols shown. This also allows to configure special symbol libs for specific projects. | + | You can either add directories of your local library separately or add a whole tree with subdirs. See above on [[#How can I set the root of my library|how to do this]]. It's a good idea to place this gafrc in your project's dir. That way, if you start gschem from some other place, you still get the system symbols shown. This also allows to configure special symbol libs for specific projects. |
geda/faq-gschem.1398444819.txt.gz · Last modified: 2014/04/25 12:53 by vzh
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
