LEF and DEF Translators

About the LEF and DEF Translators

The Library Exchange Format (LEF) and Design Exchange Format (DEF) translators read and write library and design information in LEF and DEF formats:

lef2oa translates information from LEF to the OpenAccess database.
oa2lef translates information from the OpenAccess database to the LEF file format.
def2oa translates information from DEF to the OpenAccess database.
oa2def translates information from the OpenAccess database to the DEF file format.

Library Definition File

The translator uses the library definition file when searching for or creating a new library. The library definition file is an ASCII file containing a list of libraries and their locations. The paths to the library directories specified in the library definition file can be either absolute or relative. If you define a relative path, the location of the library definition file is appended to the beginning of the path. The following is a simple example.

#tools/oa/demo lib.defs file DEFINE lib ./lib DEFINE techlib /opt/OABuilds/sun4v/oa/tools.sun4v/oa/demo/technology

Note: There are no requirements for the naming of the library definition file.

LEF and DEF Support

The translator reads LEF and DEF versions 5.3, 5.4, 5.5, and 5.6

Supported constructs in the LEF and DEF to OpenAccess translators support custom analog, digital, and mixed-signal designs. For additional information about supported and obsolete constructs, refer to the online document LEF/DEF Language Reference Manual located at http://www.openEDA.org. Select the LEF/DEF link.

Important: Before beginning a translation, read the information about LEF and DEF constructs that are not supported in OpenAccess.