You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since vcpkg always throws an error if a port from an overlay is installed and the overlay is not fed into the vcpkg call.
Furthermore ports from an overlay can also not currently be installed since this is missing from the toolchain.
I would also suggest to move all code related to manifests into a separate cmake file for better separation from what the toolchain normally should do. (Manifests are just a modular addition to it.)
The text was updated successfully, but these errors were encountered:
The problem is if somebody tries to use manifests with a vcpkg which has an (unknown to master) port installed from a port-overlay vcpkg will throw and error on the execution of the command.
Has such you might not be immediately breaking someone but locally sharing vcpkg instances becomes a bit more difficult if you have projects which could use the manifest but have other projects which requires ports from an overlay.
This shouldn't happen, since the installed directories aren't shared -- if blah is installed from an overlay in vcpkg/installed, then proj/vcpkg_installed can't know or care about blah, since it's a different installed tree.
Since vcpkg always throws an error if a port from an overlay is installed and the overlay is not fed into the vcpkg call.
Furthermore ports from an overlay can also not currently be installed since this is missing from the toolchain.
vcpkg/scripts/buildsystems/vcpkg.cmake
Lines 278 to 290 in 8133cef
I would also suggest to move all code related to manifests into a separate cmake file for better separation from what the toolchain normally should do. (Manifests are just a modular addition to it.)
The text was updated successfully, but these errors were encountered: