LTspice merging of "standard" libraries...

[Mike Deblis]

Just a thought - some of us can't use the on-line updating of LTspice, so we
lose our changes to standard.* when installing a new version over the old...

Why not have a ".include <my_standard.mos>" etc. directive for library
files. If the specifiedexternal library does not exist, silently ignore the
".include" (or provide an option to ignore/put up an error box).

If the distrubuted "standard" file has a defined ".include", then user files
can automatically be used. If ".include"s could be nested, it would allow
far better organisation of all those wretched models I have lying around...

ta,

(another) Mike

 

[Helmut Sennewald]

"Mike Deblis" <mdeblis@hotmail.com> schrieb im Newsbeitrag
news:c0ij1l$17uaq3$1@ID-219286.news.uni-berlin.de...

Just a thought - some of us can't use the on-line updating of LTspice, so
we
lose our changes to standard.* when installing a new version over the
old...

Why not have a ".include <my_standard.mos>" etc. directive for library
files. If the specifiedexternal library does not exist, silently ignore
the
".include" (or provide an option to ignore/put up an error box).

If the distrubuted "standard" file has a defined ".include", then user
files
can automatically be used. If ".include"s could be nested, it would allow
far better organisation of all those wretched models I have lying
around...

Hello Mike,
put all your private MOS models into a file named yourname.xxx and save
this file in the "cmp"-directory.
"yourname" and "xxx" may be any other characters.
Then add the line .include ../cmp/yourname.xxx to your schematic.
The default search path for include is .../lib/sub . That's the reason
why I used this ../cmp/ in front of the library filename.

The LTSPICE directory structure:
..../lib/sub
..../lib/cmp

Best Regards,
Helmut