Link Copied
Hi,
>>>The cmake I installed is 3.26.0-rc4, but I don't know what version Visual Studio is using.
You can check the cmake version being used by Visual Studio by navigating to Menu Bar
View-> Terminal -> cmake --version
In your case as you've the latest CMake already, the Visual Studio will utilize the CMake version you've installed.
Could you please check if SETVARS_CONFIG environment variable is set in your system? If not please follow the steps from the below link.
Please try to build the sample again(or the similar sample) after deleting the old sample/project.
If the issue still persists please try to reinstall Visual Studio 2019 along with Intel oneAPI Base and HPC toolkits after successful uninstallation.
Please try to install the components in the following order.
Visual Studio -> Base Toolkit -> HPC Toolkit
You should be able to see the following output in the Visual Studio after successful integration.
Please find the below link for more details.
Thank & Regards,
Shaik Rabiya
I uninstalled oneapi 2023 and then Visual Studio 2019. I installed visual studio 2022 (Version 17.5.1 - why not try a newer VS eh?) and then the Intel oneAPI Base (2023.0.0 - I made sure VS was not running when I installed oneAPI).
I deleted the example projects, and then used the VS "Extensions -> Intel -> Browse Intel oneAPI Samples" and selected the Base Vector Add example.
Unfortunately I can the same "icx-cl is not a full path and was not found in the PATH." Darn
Note that this time, the SETVARS_CONFIG is set. I am not sure if this is a remnant of what you requested I do in your previous comment, or if it's what the oneAPI Base toolkit installation did.
I checked and there is a setvars.bat in the C:\Program Files (x86)\Intel\oneAPI folder.
> dir env: | findstr -I -N oneapi
6:__VSCMD_PREINIT_PATH C:\Program Files (x86)\Intel\oneAPI\tbb\latest\redist\intel64\vc_mt\;C:\Program Files (x86)\Intel\oneAPI\tbb\lates...
7:ADVISOR_2023_DIR C:\Program Files (x86)\Intel\oneAPI\advisor\2023.0.0
41:ONEAPI_ROOT C:\Program Files (x86)\Intel\oneAPI\
64:SETVARS_CONFIG C:\Program Files (x86)\Intel\oneAPI\setvars.bat
96:VTUNE_PROFILER_2023_DIR C:\Program Files (x86)\Intel\oneAPI\vtune\2023.0.0
I must be missing a step somewhere in the VS setup.
I also used the oneAPI Tools CLI (command line interface) to create the vector add example in a different folder. I followed the vector-add\readme.md instructions and it compiled and ran ok using the CLI. This proves that the icx-cl compile tool is present, just not when using VS 2019 and 2022.
Wow, deleting SETVARS_CONFIG did the trick. Cmake ran ok and the project built. I also figured out how to build the vector_add_usm.exe. Yay!
Any idea why removing SETVARS_CONFIG fixed the problem? Back in 3-1-2023 you asked me to add it. At that time I was using VS 2019. Do you think vs 2019 was the issue?
RabiyaSK_Intel: "Could you please check if SETVARS_CONFIG environment variable is set in your system? If not please follow the steps from the below link.
Here's the successful cmake output:
1> [CMake] The CMAKE_FORCE_CXX_COMPILER macro is deprecated. Instead just set
1> [CMake] CMAKE_CXX_COMPILER and allow CMake to identify the compiler.
1> [CMake] Call Stack (most recent call first):
1> [CMake] CMakeLists.txt:8 (CMAKE_FORCE_CXX_COMPILER)
1> [CMake]
1> [CMake]
1> [CMake] -- Using the USM variant. (Eddie: this is output if u add the -DUSM=1 to CMake command arguments as shown above)
1> [CMake] -- FPGA_DEVICE was not specified.
1> [CMake] Configuring the design to run on the default FPGA device intel_a10gx_pac:pac_a10 (Intel(R) PAC with Intel Arria(R) 10 GX FPGA).
1> [CMake] Please refer to the README for information on device selection.
1> [CMake] -- Configuring done
1> [CMake] -- Generating done
1> [CMake] -- Build files have been written to: C:/temp/oneAPI/vs/Base_Vector_Add/out/build/x64-Debug
1> Extracted CMake variables.
1> Extracted source files and headers.
1> Extracted code model.
1> Extracted toolchain configurations.
1> Extracted includes paths.
1> CMake generation finished.
