I've recently noticed some path and link issues.
Windows 11 x64 (10.0.22621)
Launching MS VS 2022 community 17.8.2 from Icon yielded path issues.
Launching oneAPI CMD for x64, then running devenv (to launch MS VS) corrects the problem.
Standard CMD command prompt oneAPI related environment variables:
ADVISOR_2024_DIR=C:\Program Files (x86)\Intel\oneAPI\advisor\2024.0
...
IFORT_COMPILER24=C:\Program Files (x86)\Intel\oneAPI\compiler\2024.0\windows\
IGCCSVC_DB=AQAAANCMnd8BFdERjHoAwE/Cl+sBAAAAzgqNPpN4UkOLVIe63ZK/XwQAAAACAAAAAAAQZgAAAAEAACAAAAD8kzEW3CKAKG74BWry4kDs7H4ieDke/TIYSASNjWU9XAAAAAAOgAAAAAIAACAAAABllUIaHQHW6kioNUSehe7DQuVgvPghJwElcHLlT1LhdGAAAAB+xA6kpPMawMRVJzWs0eoTsynuCsufWblvZKURvEr2ZCBTSXIf9wkQzJVJfuj6xEbD6PG8MjMEt81awPPepVvd5lYffOfp0g6qQ4DiArDx9lhm37N/F2vhuFhI1kliZ8JAAAAAlFxtAdoWEtbaSNVR7wslZ9yC9gnADFCo3NlOu7DhACMdwmjli1HEUMt9dnDxO+HSl4YMfMGmfUEGyQIsV1FNfA==
INSPECTOR_2024_DIR=C:\Program Files (x86)\Intel\oneAPI\inspector\2024.0
...
Path=...( note, oneAPI folders not in PATH)...
...
VTUNE_PROFILER_2024_DIR=C:\Program Files (x86)\Intel\oneAPI\vtune\2024.0
...
Running the oneAPI CMD for x64 and then running devenv from threre corrects the issue.
Second issue:
With running code with "use omp_lib" and accessing OpenMP runtime library routines (e.g. omp_get_wtime())...
... but setting the Language option to .NOT. expand OpenMP directives.
Release build runs with Start and Start Without Debugging...
However, VTune will not launch application.
The work around is to add libiomp5md.lib to the link Additional Dependencies.
It is odd that the Release build links and runs but that VTune won't successfully launch the application without the additional depencency.
Jim Dempsey
