microsoft / microsoft/vcpkg

[intel-mkl] msvc msbuild linker failure

Open
#35,671 4 comments 1 reaction 1 assignee View on GitHub

@LilyWangLL is already working on this.

Since Dec 14, 2023.

category:port-bug Stale
Dominant language
CMake
Stars
27.5k
Forks
7.7k
Avg merge
2d 19h
Merged PRs (30d)
321

Description

Operating system

Windows 11

Compiler

MSVC

Steps to reproduce the behavior
Clean machine, with no intel mkl libs installed anywhere.

vcpkg install intel-mkl

build a project requiring a mkl function:

I'm using a custom static lib triplet with:
set(VCPKG_TARGET_ARCHITECTURE x64)
set(VCPKG_CRT_LINKAGE static)
set(VCPKG_LIBRARY_LINKAGE static)
Failure logs

1>Cmn64_Src_Dsp.obj : error LNK2019: unresolved external symbol DftiCreateDescriptor referenced in function "void __cdecl Dsp::Intel::FftSetupReal(struct DFTI_DESCRIPTOR * &,enum DFTI_CONFIG_VALUE,unsigned __int64)" (?FftSetupReal@Intel@Dsp@@YAXAEAPEAUDFTI_DESCRIPTOR@@W4DFTI_CONFIG_VALUE@@_K@Z)

and many more

Additional context

This occurs with the updated port file that installs intel-mkl into the vcpkg/installed folder.
Libs are install into: vcpkg/installed//lib/intel64
But linking is done with: vcpkg/installed//lib/*.lib
Copying the files from: vcpkg/installed//lib/intel64
to: vcpkg/installed//lib/

and rebuilding works correctly.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.