llvm toolchain - vcpkg integration - lld-linker error

[Neumann-A]

Using the lld-linker I get the following error:

1>lld-link.exe : error : could not open C:\Sources\Extern\vcpkg\installed\x64-windows-static\lib*.lib: invalid argument

apparently the lld-linker does not like to include libraries by wildcards.

The problem lies within:
\scripts\buildsystems\msbuild\vcpkg.targets
line 62 & 63

where
%(AdditionalDependencies);$(VcpkgRoot)debug\lib*.lib
%(AdditionalDependencies);$(VcpkgRoot)lib*.lib
is defined.

So it would be very nice if vcpkg would add and extra item for itself to the project configuration (like the llvm toolchain) so that I can easily change the values of $(VcpkgAutoLink), $(VcpkgTriplet), $(VcpkgEnabled) and maybe even $(VcpkgRoot).

[degski]

@Neumann-A lld-link has an option /lib which supposedly makes lld-link behave as lib. I don't know what that entails, because /lib has to be the first command option passed, which seems to be hard to achieve from the VC-IDE, maybe you're able to work it out.

[degski]

The LLVM Compiler Toolchain Plugin fixes the use of lld from the VS2017-IDE.

[Neumann-A]

@degski:
I am using the LLVM Toolchain Plugin from VS 2017 and lld chokes on how vcpkg autolinks if integration is installed.
Thats why #4573 simply disables autolinking if lld is used.

[degski]

@Neumann-A Sorry, I did not realize you were working on this. I guess that's not yet merged into master or what are the magic spells to end up with the vcpkg integration [as shown on your screenshot]?

As to the wild-card issue, maybe it's an idea to report that on the clang dev list, as link.exe compatibility (for lld-link.exe) is AFAIK an objective.

[Neumann-A]

@degski: https://bugs.llvm.org/show_bug.cgi?id=38985

[degski]

@Neumann-A I see.

[szabolcshorvath-craft]

Why is this issue closed? It's mid 2021 and still I get the same message:

1> lld-link : error : could not open 'C:\Users\szabolcs\vcpkg\scripts\buildsystems\msbuild......\installed\x64-windows\debug\lib*.lib': invalid argument

Environment:
Windows10, VS2019, C++, newly created Command Line Application project, Platform Toolset: llvm (clang-cl), vcpkg integration installed

Even though this issue may have been solved already, it's not clear for me, what to do to resolve this error.
Or should I open another issue for this?

[Neumann-A]

Why is this issue closed? It's mid 2021 and still I get the same message:

old integration installed? Remove it and reinstall it. This issue was also mainly for the toolset called LLVM which was installed by LLVM itself. The ClangCL toolset which gets installed by VS itself is probably not handled correctly.

you may be able to adjust the check in

vcpkg/scripts/buildsystems/msbuild/vcpkg.props

Line 26 in 5742e87

<VcpkgAutoLink Condition="'$(UseLldLink)' == 'true'">false</VcpkgAutoLink>

In the ClangCL toolset I have seen the boolean ClangClMode in ClCompile

<VcpkgAutoLink Condition="'$(UseLldLink)' == 'true' or '%(ClCompile.ClangClMode)' == 'true'">false</VcpkgAutoLink>

[szabolcshorvath-craft]

Thank you for the quick response! It's a new integration because a recent upgrade of vcpkg deleted all my previously installed packages, so I've decided to make a clean start over. But just to be sure, now I've reinstalled the integration and the problem still remains. Indeed, I'm using the LLVM platform toolset installed by VS itself. Also thank you for the tip, I will look into if I could adjust that check!

[tommitytom]

I'm getting this error on one of my AppVeyor builds too - google led me here. Unsure whether it is an issue with how I've set up the CI, or whether it's how they create the CI image. The project I'm building only contains a single .cpp file. Log here if its of any use: https://ci.appveyor.com/api/buildjobs/yh8sm1bnq63a8kcd/log

Edit: Appears to be the same issue as #15623

[Ou7law007]

How is this not solved yet? Having to disable auto link and manually link libs is not practical!

[snealbli]

I am also having this problem, identical to #4359 (comment)

Is there a solution?

[drywolf]

@ras0219-msft Looks like the temporary fix done in #4573 is no longer working ?
I am also getting the same error as mentioned by OP:

1>lld-link : error : could not open 'C:\code\vcpkg\installed\\x64-windows\debug\lib\*.lib': invalid argument

VS 2019 (16.11.7)

[gurachan]

this still an issue until this day .. xD omg..

[pudding186]

this error because you integrate vcpkg to Visual Studio , run command "vcpkg integrate remove" then everything is OK

[gurachan]

this error because you integrate vcpkg to Visual Studio , run command "vcpkg integrate remove" then everything is OK

but thats a feature xD removing a feature its a not a fix. its a temp solution u have to import manually the include and libs if u dont integrate it..

[M0n7y5]

So its a still an issue ...

[RT2Code]

I too can't build my projects with Clang without disabling the autolink feature. Is supporting both at the same time planned? It would be great, because the autolink feature is really convenient on projects with many dependencies. I think this issue should be reopened.

[dtroitskiy]

Just encountered it too.

[stxticOVFL]

this error because you integrate vcpkg to Visual Studio , run command "vcpkg integrate remove" then everything is OK

Issue is still present, this "fix" still works.

[walbourn]

#31239

[reupen]

Hi,

I just as a note for others, I have using link.exe with Clang as a workaround for this by specifying /p:PlatformToolset=ClangCL;LinkToolExe=link.exe. This stopped working following #31239.

It's easily fixed though as specifying VcpkgAutoLink=true (/p:PlatformToolset=ClangCL;LinkToolExe=link.exe;VcpkgAutoLink=true) gets things working again.