Classic Vitis IDE workspaces cannot be opened directly in Vitis Unified IDE. To facilitate the migration of projects from the classic IDE to the unified IDE, the classic IDE provides a feature to enable moving a project or workspace into the Vitis unified IDE. To use this command first launch the Vitis classic IDE on the workspace:
vitis --classic -workspace <workspace> After the Vitis IDE opens the workspace, use the command from the main menu. The tool opens a dialog box listing the projects contained in the workspace, and prompts you for a new workspace to export the projects to. Specify the new workspace location and click Finish. The tool will generate a Python migration script (migrate.py) and write it to the specified workspace folder.
After generating the migration script a pop-up window will show the location of the
script. You will need to run the script in the Vitis unified IDE by using
the vitis -s <script> form of the command as described in Launch Options.
vitis -s migrate.py| Project Type | Limitation | Workaround |
|---|---|---|
| Embedded Platforms | Local changes to BSP sources will not be migrated to the new workspace. A new BSP will be created, and the settings are applied on the new BSP. | Copy the sources to the new BSP manually. |
| Any embedded software repositories added to Vitis IDE will not be migrated. A warning will be shown in the wizard if the project has any local SW repos. |
All software repositories need to be migrated to lopper first. Refer to UG1400 for more information. The path to the migrated repository can be manually added to the migration script prior to running the script. |
|
| IP drivers includes in XSAs created with 2023.1 or older releases needs will not work. | Need to regenerate the XSA with 2023.2 release. | |
| Embedded Software Applications | Applications referring to platforms that are outside the current workspace cannot be migrated. | Migrate the platform first and update the application to use the new platform before migrating the application. |
| HW Link | Hardware linker options defined using the Extra V++ command line options will not be migrated through the script | You will need to manually define these options in the hw_link.cfg for the System project |
| Accelerated Host applications | Only compile definitions (-D), include path (-I), library paths (-L) and libraries (-l) are migrated for accelerated host applications. | Any other compiler or linker settings from the C/C++ build settings window will need to be set manually in the Application component. |