| 1.2. How Does MeVisLab Find Packages? | ||
|---|---|---|
 | Chapter 1. Package Structure in MeVisLab |  |
| 1.2. How Does MeVisLab Find Packages? | ||
|---|---|---|
| | Chapter 1. Package Structure in MeVisLab | |
MeVisLab searches in
the packages directory in which MeVisLab was installed.
the directories given in the PackagePaths settings of
mevislab.prefs.
the UserPackage path (as set in the MeVisLab Preferences dialog.
Scanning is always two levels deep, never deeper. If a package with
the same PackageIdentifier is found more than once, the last package
found will overwrite the earlier packages (in the order given above).
This way, your packages given by mevislab.prefs file or your UserPackages can overwrite installed packages.
![[Note]](images/note.png) | Note |
|---|---|
You can check your effective package structure with the tool ToolRunner. |
To compile a running MeVisLab, the packages ThirdParty, Foundation, IDE, and
Standard are required. All other packages are optional and not
required for a fully working MeVisLab installation (except that you will
not have all the nice modules from the other packages).
© 2024 MeVis Medical Solutions AG
| |  | |
| Chapter 1. Package Structure in MeVisLab |  | 1.3. Who "Knows" About Packages? |