[SYCLomatic][Doc] Add CMake script migration section in Velocity-Bench/cudaSift/README.md (#679)

Signed-off-by: chenwei.sun <[email protected]>
Co-authored-by: Wang, Zhiming <[email protected]>

Author: tomflinda

third-party-programs/Velocity-Bench/cudaSift/README.md

@@ -20,7 +20,7 @@ This file lists the detail steps to migrate CUDA version of [cudaSift](https://g
    $ export cudaSift_HOME=/path/to/Velocity-Bench/cudaSift
    $ sudo apt-get install libopencv-dev # make sure ```OpenCV*``` is installed on the machine.
    $ cd ${cudaSift_HOME}/CUDA && mkdir build
-   $ cd build && cmake ..   # make sure all dependency library are installed.
+   $ cd build && cmake -DUSE_SM=80 ..   # make sure all dependency library are installed.
 ```
 Summary of cudaSift project source code:  12 files in CUDA folder
 
@@ -70,6 +70,8 @@ $ ls compile_commands.json  # make sure compile_commands.json is generated
 compile_commands.json
 ```
 ### 3 Migrate the source code and build script
+**Follow section 3.1 or section 3.2 to migrate the source code and corresponding build scripts.**
+## 3.1 Migrate the source code and generate build script `Makefile.dpct`
 ```sh
 # From the CUDA directory as root directory:
 $ cd ${cudaSift_HOME}/CUDA
@@ -100,6 +102,70 @@ Now you can see the migrated files in the `out` folder as follow:
       └── matching.dp.cpp
 
    ```
+
+## 3.2 Migrate the source code and CMake build script
+### 3.2.1 Migrate the source code
+Run the migration command below to generate SYCL version cudaSift code:
+```sh
+$ dpct --in-root=. -p=./build/compile_commands.json --out-root=out --gen-build-script --cuda-include-path=/usr/local/cuda/include
+```
+### 3.2.2 Migrated the CMake build script
+Apply option "--migrate-build-script-only" to the migration command as follows to migrate the CMake build script:
+```
+$ dpct --in-root=. -p=./build/compile_commands.json --out-root=out --gen-build-script --cuda-include-path=/usr/local/cuda/include --migrate-build-script-only
+```
+Or, CMake script can be migrated together with cudaSift source code with the option "--migrate-build-script=CMake" as follows:
+```sh
+$ dpct --in-root=. -p=./build/compile_commands.json --out-root=out --gen-build-script --cuda-include-path=/usr/local/cuda/include --migrate-build-script=CMake
+```
+### 3.2.3 Apply necessary manual fix to SYCL version CMake build script
+Do the following changes to the migrated CMake script in the `out` directory:
+```
+diff --git /path/to/cuda/CMakeLists.txt /path/to/SYCL/CMakeLists.txt
+index d1e4b6d..ba85f53 100644
+--- a/CMakeLists.txt
++++ b/CMakeLists.txt
+@@ -56,13 +56,13 @@ set(cuda_sources
+ )
+
+ set(sources
+-  ${CMAKE_SOURCE_DIR}/../common/Utility.cpp
++  ${CMAKE_SOURCE_DIR}/common/Utility.cpp
+   geomFuncs.cpp
+   mainSift.cpp.dp.cpp
+ )
+
+ include_directories(
+-  ${CMAKE_SOURCE_DIR}/../common/
++  ${CMAKE_SOURCE_DIR}/common/
+   ${CMAKE_CURRENT_SOURCE_DIR}
+ )
+
+```
+Also copy the `common` directory to the `out` directory, using the following commands:
+```sh
+$cd ${cudaSift_HOME}/CUDA/out
+$cp ../../common/ ./ -r
+```
+### 3.2.4 Build the SYCL version cudaSift code with CMake build script
+In the `out` directory, use the following commands to build the SYCL version cudaSift:
+```sh
+$mkdir -p build
+$cd build
+$cmake -DCMAKE_C_COMPILER=icx    -DCMAKE_CXX_COMPILER=icpx -DUSE_SM=80 -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON ..
+$make
+```
+After build, the binary `cudasift` is generated in the directory `${cudaSift_HOME}/CUDA/out/build`
+### 3.2.5 Run the SYCL version cudaSift
+As the path of test data is relative to the path of CUDA version binary, the SYCL version binary should be moved to the same level directory where the CUDA version binary lies.
+Run the following commands to run the SYCL version binary.
+```
+$cp cudasift ../../build/cudasift_sycl.run
+$cd ../../build
+$./cudasift_sycl.run
+```
+
+
 ### 4 Review the migrated source code and fix all `DPCT` warnings
 
 SYCLomatic and [Intel® DPC++ Compatibility Tool](https://www.intel.com/content/www/us/en/developer/tools/oneapi/dpc-compatibility-tool.html) define a list of `DPCT` warnings and embed the warning in migrated source code if need manual effort to check. All the warnings in the migrated code should be reviewed and fixed. For detail of `DPCT` warnings and corresponding fix examples, refer to [Intel® DPC++ Compatibility Tool Developer Guide and Reference](https://www.intel.com/content/www/us/en/develop/documentation/intel-dpcpp-compatibility-tool-user-guide/top/diagnostics-reference.html) or [SYCLomatic doc page](https://oneapi-src.github.io/SYCLomatic/dev_guide/diagnostics-reference.html). 
@@ -153,7 +219,7 @@ If an error occurs during runtime, refer to [Diagnostics Utility for Intel® one
 * Command Line Options of [SYCLomatic](https://oneapi-src.github.io/SYCLomatic/dev_guide/command-line-options-reference.html) or [Intel® DPC++ Compatibility Tool](https://software.intel.com/content/www/us/en/develop/documentation/intel-dpcpp-compatibility-tool-user-guide/top/command-line-options-reference.html)
 * [oneAPI GPU Optimization Guide](https://www.intel.com/content/www/us/en/docs/oneapi/optimization-guide-gpu/)
 * [SYCLomatic project](https://github.com/oneapi-src/SYCLomatic/)
-
+* [Migrate a CMake Build Script](https://github.com/oneapi-src/SYCLomatic/blob/SYCLomatic/docs/dev_guide/migration/migrate-cmake-build.rst)
 
 ## Trademarks information
 Intel, the Intel logo, and other Intel marks are trademarks of Intel Corporation or its subsidiaries.<br>