Attempting to launch a DPC++ app (.exe) on windows os, results in an error message as shown below.
What could cause this error? What are the redistribution requirements/packages?
- General Support
Installing the latest base kit version "w_BaseKit_b_2021.1.4.423" has NOT fixed this problem.
Following the errors and placing "sycl.dll" side by side with the executable, then "libmmd.dll" then "pi_opencl.dll"
resulted in a silent app termination without exec, no shutdown, no clean-up.
The directory structure is intact, and relevant to "ONEAPI_ROOT", but not drive "C", are there hard coded paths?
Apparently, I'm missing the redistributables...
What are the redistributable requirements?
Deploying the following shared libraries side by side with the executable seems to work. Not tested on an external (oneAPI not installed) windows environment.
Check your installation once and if needed reinstall the base toolkit.
Because for us the latest base-kit is working fine on windows 10 OS without any .dll error and without explicitly linking libraries.
Running an executable in the development time works well, using Intel oneAPI command prompt or MS-VS.
I have "w_BaseKit_b_2021.1.4.423".
The directory structure is intact, and relevant to "ONEAPI_ROOT".
The issue here is about launching the same executable from outside the development environment. Please try to double click it or call it from the standard cmd, in order to reproduce this issue.
I came to know your problem when you are double-clicking the executable(outside dev environment) it's showing "sycl.dll not found".
This error will persist because you are not in inteloneapi environment, before running that executable it's mandatory to source the environment in the same session, for this you have to execute %ONEAPI_ROOT%setvars.bat in the same session where you want to run the executable.
You can open the CMD in the same directory(executable directory eg vector-add.exe) and first ran the setvarsh.bat file then your executable(eg vector-add.exe) it will run without error.
Launching a DPC++ app and overcoming linking issues in a development machin is considered solved following this thread.
Launching a DPC++ app in an external environment where oneAPI is not installed, discussion is continued at thread:
Thank you for your care.