-
Notifications
You must be signed in to change notification settings - Fork 6.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot find boost after migration to manifest mode #38823
Comments
You should put these files in the same folder your root CMakeLists.txt is located.
These steps are unnecessary. Vcpkg toolchain will call |
I put vcpkg.json & vcpkg-configuration.json under app root dir. Now I got this? Did I miss something? |
Can't say without proper configure log. |
Could you please provide your CMakeLists.txt file? |
Hi, I played with it a little more, and the build passed, though I didn't know why :( I do have some questions:
|
|
follow up of question 1: for Visual Studio, running "vcpkg.exe integrate install" under VCPKG_ROOT is needed, right? another question:
|
|
|
|
|
At this point you should start using search engines ;) |
Thanks guys. I have one last question:
Then I tried manifest mode, using the same baseline, it works without this issue. How come this difference? |
You seem to use an old checkout in classic mode, so old central scripts want to use old URLs which no longer work. |
Describe the bug
We used to build our app against vcpkg in classic mode. It worked. Now we want to change to manifest mode. But after changing, we got an error:
This error persists, even when I force boost's version to the same to classic mode.
The vcpkg.json and vcpkg-configuration.json is here:
vcpkg.json
vcpkg-configuration.json
Environment
To Reproduce
Steps to reproduce the behavior:
put vcpkg.json & vcpkg-configuration.json under vcpkg dir
.\vcpkg.exe integrate install
.\vcpkg.exe install
cmake -Bbuild -S. -DCMAKE_TOOLCHAIN_FILE:STRING=D:\vcpkg\scripts\buildsystems\vcpkg.cmake
The text was updated successfully, but these errors were encountered: