oneAPI Registration, Download, Licensing and Installation
Support for Getting Started questions related to download, Installation and licensing for Intel oneAPI Toolkits and software development tools.
1261 Discussions

OneMKL with VS Integration (for msbuild) failing on GitHub Actions

AlexHarker
Beginner
501 Views

I'm trying to install OneMKL in a remote CI situation in order to compile a VS solution that requires it. On my local machine I have installed the oneAPI Base Toolkit and setup the solution accordingly and it compiles fine.

 

On CI I run the following in bash:

 
env:
  WIN_ONEAPI: https://registrationcenter-download.intel.com/akdlm/IRC_NAS/18723/w_onemkl_p_2022.1.0.192_offline.exe
 
mkdir install
cd install
url $WIN_ONEAPI --output oneapi_install.exe
/oneapi_install.exe -s -x -f webimage_extracted --log extract.log
/webimage_extracted/bootstrapper.exe -s --action install --eula accept -p=NEED_VS2022_INTEGRATION=1

The installation reports as as successful:

 

Installed Location: C:\Program Files (x86)\Intel\oneAPI

Installation has successfully completed

 

I then use msbuild to build the solution but I get the error that:

Cannot open include file: 'mkl_vml.h': No such file or directory

 

This suggests that the VS integration has not worked correctly and no matter what combinations I try I can't seem to get it to work (I have use the whole of the base toolkit also, but I only require oneMKL for the actual compile and in any case this didn't work either).

 

I'd be very grateful for pointers to try, as I am out of ideas. The whole action is here should it be relevant https://github.com/AlexHarker/AHarker_Externals/actions/runs/2641619234/workflow

 

Thanks

0 Kudos
2 Replies
AlexHarker
Beginner
500 Views

Also perhaps worth noting is that I set up msbuild prior to adding oneMKL. Not sure if that matters.

0 Kudos
AlexHarker
Beginner
485 Views

Looks like this might be working if I set the machine (and VS) to 2019, rather than latest (2022). I'm not sure if this is related to the sticky issue on the forum here, but I don't get any installation errors either way - just a broken compile on 2022. I'm running a test now to double-check that 2019 works - if not I'll post back.

0 Kudos
Reply