Skip to content
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

[boost] build failure #38487

Closed
SKNo opened this issue Apr 30, 2024 · 6 comments
Closed

[boost] build failure #38487

SKNo opened this issue Apr 30, 2024 · 6 comments
Assignees
Labels
category:question This issue is a question

Comments

@SKNo
Copy link

SKNo commented Apr 30, 2024

Operating system

Windows

Compiler

MSVC

Steps to reproduce the behavior

git pull
vcpkg upgrade --no-dry-run

Failure logs

error: The control or manifest file for boost-vcpkg-helpers could not be loaded due to the following error. Please remove boost-vcpkg-helpers and try again.)
E:\Lib\vcpkg\ports\boost-vcpkg-helpers: error: boost-vcpkg-helpers dies not exist

Additional context

It happend after git pull (including the latest version of boost)

@SKNo SKNo added the category:port-bug The issue is with a library, which is something the port should already support label Apr 30, 2024
@Neumann-A
Copy link
Contributor

boost-vcpkg-helpers has been removed. Be aware that vcpkg upgrade is not really a supported command since it is not transactional

@SKNo
Copy link
Author

SKNo commented Apr 30, 2024

@Neumann-A
I am confused : what would be the command to upgrade all updated softwares and their dependencies after a git pull
Thank you

@Neumann-A
Copy link
Contributor

Either use a manifest which automatically rebuilds everything (and deletes as needed) or delete your installed tree manually and rebuild everything manually.
vcpkg upgrade is not transactional; it just exists for historic reasons.

@SKNo
Copy link
Author

SKNo commented Apr 30, 2024

Thank you @Neumann-A
I've always looked at vcpkg upgrade as a usefull one-liner similar to conda update --all
Is there an example for such a manifest or should I go through documentations?
Thanks again

@Neumann-A
Copy link
Contributor

Is there an example for such a manifest or should I go through documentations?

Manifest is just a vcpkg.json. All ports have such a file. For usage having only the dependencies field is theoretical enough. You can use --x-manifest-root=<manifest-dir> if you do not want to have the manifest in the same directory as vcpkg.

@LilyWangLL LilyWangLL added category:question This issue is a question and removed category:port-bug The issue is with a library, which is something the port should already support labels May 7, 2024
@LilyWangLL
Copy link
Contributor

We hope your question was answered to your satisfaction; if it wasn't, you can reopen with more info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:question This issue is a question
Projects
None yet
Development

No branches or pull requests

3 participants