Closed Sn1cket closed 1 year ago
This looks suspiciously similar to #37. Can you try switching to the pre-release channel and using the new vcpkg.storageLocation
setting (as described in this comment) to see if this is a long path issue? That setting should be available in on the official channel in the next few days once we ship a new official release.
I tested the version on the pre-release channel and the problem is fixed when using a different location than the default. So it seems to be a long path issue. Thanks for your help!
Great! Marking as fixed pending release.
The vcpkg.storageLocation
setting is now available in the official 0.7.0 release.
Type: Bug Report
Describe the bug
The issue persists after disabling the extensions.
I followed this article to bootstrap my dev environment with vcpkg: https://devblogs.microsoft.com/cppblog/vcpkg-artifacts First I tried to build the example project all in VS Code with the vcpkg environment activated like described in the article and this worked fine. Then I changed the extension of main.c to main.cpp and I made a few C++ compatibility changes to the project. You can find the changes in my fork of the getting-started repo (https://github.com/Sn1cket/getting-started/tree/build_with_cpp) In this state I am able to build the project when I run the following commands in a terminal:
The problem starts when I try to do the same in VS Code. I am getting the following error when compiling the main.cpp file:
It seems like the compiler include paths don't get resolved properly in the VS Code vcpkg environment.
To Reproduce Steps to reproduce the behavior:
Expected behavior I expect the build to finish like outside of the terminal
Code sample and logs