vcpkg.json reusage

[matwey]

Hello,

I have a project. It is C++ library using CMake as a build system. Inside, I also have vcpkg.json and vcpkg-configuration.json to be able to install requires vcpkg dependencies in a manifest mode.

Now I am going to create a vcpkg port for my application in a private vcpkg registry. To make a port I need to have vcpkg.json inside the port directory. Is it possible to avoid repeating myself and reuse one vcpkg.json instead on another? I don't want to manage two dependency lists at different places.

[dg0yt]

IMO there is no trivial solution for using the same file.

• One file lives in the source repository and acts as a "top-level" manifest. It is not seen before unpacking the sources and building the package.
• One files live in the port directory in the registry. It provides a dependency to an external top-level install request. It is evaluated long before fetching and unpacking the package's sources.
• For the same file, it might be surprising that some properties such as default-features have different effects for a top-level manifest vs. a port manifest.

[matwey]

• For the same file, it might be surprising that some properties such as default-features have different effects for a top-level manifest vs. a port manifest.

Indeed, you are right. For instance, it is unlikely that I need to build examples and unit tests in case of the port, while for development they are crucial.