Distributed DLLs built with /Qparallel option do not work on client computers

[avinashs]

I recently added the /Qparallel option to build the new version of a DLL that I distribute to other users in the organization and other computers that I use. However, addition of the option causes the DLL to fail on the client computers other than the one where it was built. Rebuilding with the /Qparallel option removed restores the functionality of the DLL. What could be causing this problem? Will add that some of the client computers have Intel oneAPI installed and the DLL does not work on them either.

[andrew_4619]

You need to install the redistributables if you do a build parallel software as some of the required lib are not available for static builds.

[avinashs]

Thanks, @andrew_4619 . On one of the machines, the redistributables were installed along with oneAPI but no success there either. Currently have removed the /Qparallel option since it did not seem to make any difference in execution speed.

[IanH]

Guessing a little as to the precise meaning of "causes the DLL to fail", have you tried using tools such as Dependency Walker (or a modern equivalent like Dependencies), on the target machine, within the target environment, to diagnose DLL loading issues?