Colin D Bennett wrote: > No big deal, just copy the symbols from the component > library into your new design project's Symbols directory as you need > them. This small effort is, for me, completely worth it for the > robustness provided by avoiding dependency on external symbol > libraries. It allows me to feel bold about making improvements to my > symbol library without requiring extreme measures to ensure > compatibility with existing schematics.
gschem almost allows a much more convenient way: 1) Draw the schematics with symbols from a central lib. 2) embed all the symbols in the schematics. This puts a copy of the symbol in the *.sch file rather than just a reference. That way, changes in the lib do not affect the schematic at all. Unfortunately, does exactly the opposite. That is, it removes the local copy of the symbol in favor of a rererence to a sym-file in the library. The nasty side effect is that you may get an incompatible version of the symbol. In addition, there is no way to export the embedded symbol to some local directory. (Of course you can use a text editor and copy/paste) The export-symbols action is one of my most favorite feature requests for gschem. Maybe, I am going to write a third party helper script to extract all embedded symbols with awk... ---<)kaimartin(>--- -- Kai-Martin Knaak Email: k...@familieknaak.de http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53 not happy with moderation of geda-user _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
