However if your project is from a previous release (2024.2, 2024.1 or 2023.2) you can follow the tutorial on this page for using the migration utility. There is a script supplied in this tutorial that will build a Vitis Classic Workspace. Follow the steps below to generate this workspace
Launch XSCT, and use the command below
cd scripts
make all
This will create the platform xsa file and the classic_workspace workspace. Launch Vitis Classic, and navigate to the workspace created above.
The script above will set the app C/C++ build settings with an EXAMPLE_SYMBOL.
To test the BSP settings, the script will update the extra_compiler_option in the BSP to append the “-pg” option.
I also added the xilffs library to the BSP.
Note: These are just for demonstration purposes.
Follow the steps below to migrate this Classic workspace to Unified workspace.
Vitis -> Export Workspace to Unified IDE
Choose the Vitis Unified workspace location.
This will generate a migration.py python script that can be opened in the Vitis Unified IDE. First, close Vitis Classic IDE and follow the steps below.
cd path/to/unified_workspace
vitis -s migrate.py
Once the script is complete, launch the Vitis Unified IDE and set the workspace to the newly generate unified_workspace.
Open the UserConfig.cmake as shown below to verify that the symbol has been migrated.
Open the Vitis-comp.json as shown below to verify that the xilfss driver is migrated.
Open the Vitis-comp.json as drop the psu_cortexa53_0 and verify that the proc_extra_compiler_flags is appended as expected with “-pg”.