User Guide

Table Of Contents
Thiscanalsobedoneatthecommandline:
RENAMEDIL16DIL-16;
ThepackageDIL16getsthenewnameDIL-16.
The device, symbol, or package name may also be given with its exten
-
sion(.dev, .sym, .pac),forexample:
REMOVEDIL16.PAC
In this case it is not necessary to switch to the related editing mode
before.
UpdatePackagesinLibraries
As already mentioned in the section Copying of Library Elements it is
possible to copy packages from one library into another one. An already
existingpackageisreplacedinthatcase.
Each library contains packages which are needed for device definitions.
In many libraries identical types of packages can be found. To keep them
uniform over all libraries it is possible to replace all packages of a library
with those of another library with the help of the UPDATE command.
An existing package with the proper name will be replaced by the cur
-
rentdefinition.
If you have, for example, special requirements for packages you could
define them in a custom-built package or SMD library. The UPDATE
commandcouldtransferthemtootherlibraries.
Therefore open the library to be updated und select Library/Update....
Nowselectthelibrarywhichyouwanttotakethepackagesfrom.
HavingfinishedtheupdateEAGLEreportsinthestatusbar:
Update:finished-librarymodified!
Iftherewasnothingtoreplace: Update:finished-nothingtodo.
Itisalsopossibletousethecommadlineforthisprocedure.
If you want to update your library with packages from, for example,
dil.lbr,type:
UPDATEdil.lbr
Totransferpackagesfromdifferentlibraries,typeinoneafteranother:
UPDATEdil.lbrsmd.lbrspecial.lbr
Toupdateasinglepackage,typeinthepackagename:
UPDATESO14@smd
The extension .lbr is not necessary. You may also use the whole library
path.Seepage 207 forfurtherinformation.
209
ComponentDesignExplainedthroughExamples