Overlay Port not picking up vcpkg.json

[diehard2]

I'm trying to load an overlay port as follows

set(SOURCE_PATH "/home/dev/my_library")

vcpkg_cmake_configure(
    SOURCE_PATH ${SOURCE_PATH}
    OPTIONS
        ${FEATURE_OPTIONS}
        -DVERSION=${VERSION}
)

vcpkg_cmake_install()
vcpkg_copy_pdbs()

vcpkg_cmake_config_fixup(PACKAGE_NAME ${NAME} CONFIG_PATH "lib/cmake/${PORT}")


file(REMOVE_RECURSE "${CURRENT_PACKAGES_DIR}/debug/include")
file(REMOVE_RECURSE "${CURRENT_PACKAGES_DIR}/debug/share")                

there's a very simple vcpkg.json in my overlay port directory

{
    "name": "my-library",
    "version": "0.0.1",
    "dependencies": [
        {
            "name": "vcpkg-cmake",
            "host": true
        },
        {
            "name": "vcpkg-cmake-config",
            "host": true
        }
    ]
}

The location on disk (at "/home/dev/my_library") has its own vcpkg.json, however the overlay port isn't picking this up. If I create a regular port for a custom registry, it respects the vcpkg.json in the repo it pulls from github. Is this just not supported for overlay ports?

[Osyotr]

Overlay port manifest should bring all dependencies of the package it's trying to build. Vcpkg can't dynamically add dependencies based on the manifest in package's sources.

[diehard2]

@Osyotr it pulls it in if I have a private registry, I would expect it to do the same thing for an overlay port. Are you sure this isn't an oversight?

My motivation for the source based overlay port is I sometimes need to debug the source of a package, but I can't keep all of the buildtree around since I'm on a shared resource. Additionally, I can't modify the source in the buildtree in manifest mode and see if the changes fix things.

I can work around it, it was just somewhat unexpected

[Osyotr]

By the time portfile.cmake (from overlay port or from port in a registry) is executed, all dependencies are already satisfied. I don't know how your registry is set up so I can't say anything about it.