It seems that the registry values, provided by 'reg_keys.json' (in offline install package) do not correspond to the expected values in the Build Target files (xxxxxxoneMKL.v142.props) for Microsoft Visual Studio 2019. I've tracked down the issue to the following RegistryKey families missing:
HKLCU\SOFTWARE\Intel\PerfLibSuites\SelectedTools\**
HKLM\SOFTWARE\Intel\PerfLibSuites\Defaults\**
From Intel.Libs.oneMKL.v142.props:
<_oneMKLSubKey Condition="'$(_oneMKLSubKey)'==''">$([MSBuild]::GetRegistryValueFromView('HKEY_CURRENT_USER\Software\Intel\PerfLibSuites\SelectedTools\VS16\oneMKL\$(ICPlatform)', 'SubKey', null, RegistryView.Registry32))</_oneMKLSubKey>
...
<_oneMKLSubKey Condition="'$(oneMKLMajorVersion)'==''">$([MSBuild]::GetRegistryValueFromView('HKEY_LOCAL_MACHINE\SOFTWARE\Intel\PerfLibSuites\Defaults\$(ICPlatform)', 'oneMKLSubKey', null, RegistryView.Registry32))</_oneMKLSubKey>
Installed on two different machines - same result, which is not a surprise, after I traced the install logs to the 'reg_keys.json' contents.
I've managed to recreate the expected keys in a way aligned with a custom .props file. But now I see this is the same for TBB, and I have to recreate it's RegKeys also...
Will this be different if I install the entire oneAPI Base package which I'm avoiding, as I only use the MKL/TBB libraries?
P.S. Also when it finally worked, I get only linking against the DLL interface (mkl_core_dll.lib), even if I specify the mkl_core.lib in the input to the linker.
