Replies: 1 comment
-
Not really the answer, but a workaround you can try, and the recommended way of doing it to use fmt is to download it using CMake FetchContent, here's how i have it setup for one of my projects, CMakeLists.txt: Fetch fmt library and make it availableinclude(FetchContent) add_executable(${PROJECT_NAME} Make sure the following are below your add_executableLink the fmt library and include its headerstarget_link_libraries(${PROJECT_NAME} fmt::fmt) Include fmt headers directorytarget_include_directories(${PROJECT_NAME} PRIVATE ${fmt_SOURCE_DIR}/include) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I've found a couple of threads that kind of/sort of discuss the issue I'm having, but none of them helped:
I have a pretty simple project resulting from following the tutorial in the Microsoft Docs to get a project using vcpkg to work with VS Code. It consists of the following files:
CMakeLists.txt
CMakePresets.json
GdalCppProject.cpp
vcpkg-configuration.json
vcpkg.json
The project builds, runs and debugs fine in VS Code, but line 1 of GdalCppProject.cpp is underlined with a red squiggly line and I get the following problem:
How do I get the extension to recognize dependencies managed with
vcpkg
? The only C++ relevant extensions I have activated are the C/C++ and the CMake Tools extensions by Microsoft.Beta Was this translation helpful? Give feedback.
All reactions