Visual Studio 2015项目如何通过.props文件继承Intel性能库配置？

Hey, I’ve hit this exact snag with Intel MKL and Visual Studio property sheets before—let’s walk through the most likely culprits and fixes:

1. You’re missing the Intel MKL built-in property sheet import #

The "Use Intel MKL" toggle in project properties doesn’t just set a simple boolean—it triggers a chain of configurations (include paths, library links, preprocessor defines) via Intel’s own property sheet. If your custom .props file only sets the UseIntelMKL flag manually without importing Intel’s official sheet, it won’t work.

Open your .props file and add this import group (adjust the path if your MKL installation is in a different location):

<ImportGroup Label="PropertySheets">
  <Import Project="$(MKLROOT)\tools\builder\intel_mkl.props" Condition="Exists('$(MKLROOT)\tools\builder\intel_mkl.props')" />
</ImportGroup>

The Condition ensures it only loads if MKL is installed at the expected path.

2. Verify platform/architecture alignment #

MKL’s libraries are split by x86/x64, so your property sheet needs to target the correct platform. Add conditional properties to match your project’s architecture:

<PropertyGroup Condition="'$(Platform)'=='x64'">
  <MKLROOT>C:\Program Files (x86)\IntelSWTools\compilers_and_libraries\windows\mkl</MKLROOT>
</PropertyGroup>
<PropertyGroup Condition="'$(Platform)'=='Win32'">
  <MKLROOT>C:\Program Files (x86)\IntelSWTools\compilers_and_libraries\windows\mkl</MKLROOT>
</PropertyGroup>

Also, confirm the $(MKLROOT) environment variable is set correctly in VS—sometimes system environment variables don’t propagate to the VS process, so hardcoding the path (temporarily) can help test.

3. Check if properties are actually being inherited #

To confirm your .props is applying MKL settings:

• Right-click your project → Properties
• Navigate to C/C++ → General → Additional Include Directories
• Click the dropdown → Edit
• Look for entries from your property sheet (they’ll be labeled with the .props filename). If there’s no sign of MKL’s include path, your sheet’s conditions might be wrong, or you’re using the wrong property names (Intel uses specific property keys like IntelMKLIncludeDirs instead of generic ones).

4. Ensure Intel Compiler Toolset is active #

The "Use Intel MKL" option only fully works when the Intel C++ Compiler toolset is selected for your project. Go to Project Properties → General → Platform Toolset and make sure it’s set to an Intel toolset (e.g., Intel C++ Compiler 19.0) instead of the default MSVC toolset.

5. Fallback: Manually replicate MKL configurations #

If importing the Intel property sheet fails, copy all the MKL-related settings from a working project into your .props file. For example:

<PropertyGroup>
  <PreprocessorDefinitions>_MKL_ILP64;MKL_DIRECT_CALL;%(PreprocessorDefinitions)</PreprocessorDefinitions>
  <AdditionalIncludeDirectories>$(MKLROOT)\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
</PropertyGroup>
<ItemDefinitionGroup Condition="'$(Platform)'=='x64'">
  <Link>
    <AdditionalLibraryDirectories>$(MKLROOT)\lib\intel64;%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
    <AdditionalDependencies>mkl_intel_lp64.lib;mkl_core.lib;mkl_sequential.lib;%(AdditionalDependencies)</AdditionalDependencies>
  </Link>
</ItemDefinitionGroup>

The %(...) ensures you don’t overwrite existing project settings—you’re appending MKL’s config to them.

内容的提问来源于stack exchange，提问作者Hexx i.m