Unknown --project argument about arm-learning-paths

[pareenaverma]

Hi @Zitrax thank you for reporting this issue. You are right, --project is an invalid option. You should use --json to point to the location of the json file.

The command should be:
vcpkg activate --json=../my-config.json

I will close this issue once the fix is merged into production.

Thank you!

[Zitrax]

--json seem to be documented as:

Full path to JSON file where environment variables and other properties are recorded

So that does not seem to be the way of pointing to a manifest file, actually using it overwrote my manifest file with some json output - so this is something different.

The only way I found so far that seem to do something similar is --x-manifest-root, although it points to a directory containing the vcpkg-configuration.json file, it does not directly point to a file.

[pareenaverma]

Hi @Zitrax thanks for reporting that back. I'm checking if there's an option to point directly to a manifest file instead of a directory containing the manifest file.

[Zitrax]

Related I found this commit: microsoft/vcpkg-tool@3247920 which seem to indicate that --project existed earlier but was reverted for some reason.

[KeilChris]

Hello @Zitrax , you are correct - the feature has been removed. We will also remove this from the learning path. Unfortunately, the "warning: vcpkg-artifacts is experimental and may change at any time." is true...

[pareenaverma]

Removed the option in PR #692