DVT provides an OVM to UVM migration wizard which automatically performs all the necessary changes within an existing OVM project. The changes may also be reviewed and customized.
Right click on a project/file/directory in the navigator, then select Refactor -> Migrate OVM to UVM. You can also perform this action for multiple selected resources.
In the first page of the wizard you can configure:
1. What to replace, as a comma separated list of strings which will be replaced in the code
2. Replacement, as a comma separated list of strings of replacements corresponding to the elements of the list at 1.
3. Exceptions, as a comma separated list of strings which may match a string in 1. but you would like to leave as-is
4. File/folder name updating - check this if you also want to migrate file and directory names. Note that exceptions are not applied in this case.
5. Disabling OVM Project, in case your project is configured with DVT as an OVM project, the wizard removes this configuration.
6. Enabling UVM Project, in case your project is not configured with DVT as an UVM project, the wizard adds this configuration.
1. UVM library path - if you enable UVM, the UVM library is compiled up-front, and you must specify its location. You can may use system variables ($UVM_HOME in the snapshot below).
2. Link Resources - for quick navigation in the library code, you may link (logical link, nothing is created on disk) the library files to your project. This way, although outside your project, the UVM sources will not be shown with gray icons and limited functionality.
In the review page you can inspect the changes that will be performed, and filter out (uncheck) the changes you don't want to perform.
