VCPKG in latest clion is a nightmare
Answered
Yo
It's very frustrating.
I have vcpkg, made a new folder for it, let it install from 0 , let it configure >
vcpkg.json
{
"name" : "c-dll-python-01",
"version-string" : "1.0.0",
"builtin-baseline" : "91dd61bd441a68b4017b61011d0350b2e6aeeccf",
"dependencies" : [ {
"name" : "python3"
}, {
"name" : "pybind11",
"version>=" : "2.10.0#1"
} ],
"overrides" : [ {
"name" : "python3",
"version" : "3.7.3"
} ]
}
But even tho it has it, it does not display them as installed
Clion injecks vcpkg variables as black magic.
NONE of them work, I installed specific version of python 3.7.3 and yet find package return 3.9 from os.
Even if I disable vcpkg plugin/etc he still uses vcpkg, I HAVE NO IDEA HOW!!!
Frustrating as "!%!"£%!"^.
God I miss clion back from 2016/17 years when the app just worked. Now its bloated, laggy, crashing crap ;[
Please sign in to leave a comment.
Hello!
The thing is that vcpkg has two modes of consuming dependencies - classic mode and manifest mode.
In classic mode, vcpkg produces an "installed" tree which is associated with the vcpkg installation, not an individual project. In other words, vcpkg maintains a central installed tree inside the vcpkg instance.
In manifest mode, on the contrary, an installed tree is associated with a particular project rather than the vcpkg installation and is placed in the project directory or build directory.
In the Vcpkg tool window CLion shows only the packages installed inside the vcpkg instance.
Presence of vcpkg.json means that you use vcpkg in manifest mode and the packages are installed in the project directory or build directory. Therefore they are not shown in the Vcpkg tool window.
Hope it's more clear now.
>Even if I disable vcpkg plugin/etc he still uses vcpkg
Disabling the plugin disables only the vcpkg integration in CLion. You will still have the CMake profile (`File | Settings | Build, Execution, Deployment | CMake`) with `-DCMAKE_TOOLCHAIN_FILE` even after disabling the plugin, and therefore vcpkg will still be used in your project.
>God I miss clion back from 2016/17 years when the app just worked
You can always find previous CLion version here https://www.jetbrains.com/clion/download/other.html.