manifest not supported ? about run-vcpkg

[Milerius]

Little update, it's seems that with manifest approach all libraries are rebuild each push

[lukka]

@Milerius there is not first class support for manifest files yet. Contributions are welcome!

Currently, there are ways to make it working, e.g.

• do not pass any argument in vcpkgArguments input, but set the VCPKG_FEATURE_FLAGS environment variable instead.
• pass input setupOnly:true, and then afterwards run the commands you need in a run: step.

[Milerius]

Ok @lukka what about caching ? Because it's seems now vcpkg use a default data folder to save binary but it's not cached by this action yet

[lukka]

@Milerius the automatic caching only saves the known directories relative to $VCPKG_ROOT (e.g. installed). If there is a way to tell vcpkg to store artifacts under any non excluded subdirectory in there, it will be saved.

[spinicist]

Currently I have an (old) response_file.txt and a vcpkg.json manifest file in the same repo. I think all my dependencies are being built twice?

[lukka]

Released run-vcpkg@v6 that contains docs and sample about using vcpkg.json manifest file. Feedback is welcome!