If your project uses Microsoft Visual Studio, you can use the --vcxprojfile option to point to the project that requires migration. The Intel® DPC++ Compatibility Tool will migrate the files you provided as input files. For example:
dpct --vcxprojfile=vector-add.vcxproj --in-root=./ --out-root=output_proj src\vector_add.cu
The command specified above migrates src\vector_add.cu, which is part of vector-add.vcxproj. The result of the migration is sent to the output_proj folder.
-OR-
dpct --vcxprojfile=vector-add.vcxproj --in-root=./ --out-root=output_proj
The command specified above migrates all relevant files the tool found in vector-add.vcxproj. The result of the migration is sent to the output_proj folder.
You can use the Intel® DPC++ Compatibility Tool within the Microsoft Visual Studio IDE to migrate your project to a DPC++ project.
Step 1: Select an Existing Project and Start Migration
To select an existing project in Microsoft Visual Studio and start migration:
Step 2: Specify the Migration Configuration
After selecting an existing project, you will see the Migration Configuration dialog. These configurations have default values. You are able to specify the configurations, including the new project file name and directory, the --in-root argument, and the additional options for the migration. The command line area is read-only and shows the command line that will be used to migrate the project. The migration starts once you click OK.
Step 3: Verify the Source for Correctness
Verify the migration of the source code that uses variables that are declared using preprocessor directives. Inspect the migrated source code, address any DPCT warnings generated, and verify correctness of the new program. For the most accurate and detailed instructions on addressing warnings, see the Addressing Warnings in the Migrated Code section of the sample README files.
The Intel® DPC++ Compatibility Tool notes the places in the code that may require your attention during the migration of the files in order to make the code DPC++ compliant or correct. Comments are inserted into the generated source files and displayed as warnings in the output. For more details on what a particular warning means, see the Diagnostic Reference . An example is below:
/path/to/file.hpp:26:1: warning: DPCT1003:0: Migrated API does not return error code. (*,0) is inserted. You may need to rewrite this code.
// source code line for which warning was generated
^
Step 4: Check the Detailed Diagnostic Messages
To learn more details about a diagnostic message, click the Help hyperlink in the Actions column, which is located in the table in the Intel® DPC++ Compatibility Tool view. The detail about why the diagnostic message is generated and information on how to fix the issue are shown.
Specifying Options
You can set your preferences for using the Intel® DPC++ Compatibility Tool within Microsoft Visual Studio:
If you have multiple versions of the Intel® DPC++ Compatibility Tool installed, you can select which version to use.