Section 8: Keithley User Library Tool (KULT)
Model 4200A-SCS Parameter Analyzer Reference Manual
8-54
4200A-901-01 Rev. C / February 2017
Usage
kult bld_lib -l<
library_name
> [
options
]
Builds the <
library_name
> user library in the active user-library directory.
Any of the following may be placed at the [
options
] position in the command:
•
-dep <library_dep_1>...[library_dep_6]
Specifies up to six user libraries upon which
library_name
depends.
Dependent user libraries must be in the active user-library directory. For more information about
dependent libraries, refer to
Working with interdependent user modules and user libraries
•
+hide
Hides
library_name
so that it is not visible in Clarius.
•
-hide
Shows
library_name
so that it is visible in Clarius.
Working with interdependent user modules and user libraries
KULT allows a user module to call other user modules. A called user module can be in the same user
library as the calling module, or can be in another user library. When the module that you are creating
calls a module in another user library, you must:
1. Select
Options > Library Dependencies
.
2. Specify each called library from the list that is displayed.
You must select user module and user-library dependencies carefully. Observe the following:
•
Try to put user modules with interdependencies in the same user library and minimize the number
of interdependencies between libraries. This practice helps to avoid problematic user library
dependency loops (
Lib1
relies on
Lib2
,
Lib2
relies on
Lib3
,
Lib3
relies on
Lib1
).
•
If a user module in one user library must depend on user modules in other user libraries, take
care when selecting the user libraries to be linked with the user module under development. The
next section provides guidance.
The user libraries to be linked are saved so that future rebuilds do not require the dependencies to
be reselected. This information is stored in the
<
library_name
>_modules.mak
file in the
%KI_KULT_PATH%\<
library_name
>\kitt_obj
directory.
•
Structure dependencies hierarchically to avoid circular dependencies, and then build the
dependent user libraries in the correct order. The next two sections provide guidance.
