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
conan cache path only allows querying the export_source, source, build, and metadata folders. It seems that the package folder, containing the final binaries, cannot be queried? Is that an oversight?
Have you read the CONTRIBUTING guide?
I've read the CONTRIBUTING guide
The text was updated successfully, but these errors were encountered:
If you provide the reference with the package_id or the package_id + package_revision the package folder should be shown by default. Like this, for example:
# outputs the package folder for the latest package revision:
$ conan cache path zlib/1.2.13#e377bee636333ae348d51ca90874e353
/<path_to_local_cache>/.conan2/p/b/zlib27fc03271dsd3/p
# outputs the package folder for the specific package revision:
$ conan cache path zlib/1.2.13#e377bee636333ae348d51ca90874e353:6fe7fa69f760aee504e0be85c12b2327c716f9e7#90be0436f7d56b2561466a5914ecd2f1
/<path_to_local_cache>/.conan2/p/b/zlib27d3dds71f7ab/p
@czoido Maybe it would also be useful to allow export and package options in the --folder argument. IMO it's confusing (and very uncommon compared to other CLI tools) to have different behavior when not specifying such an argument instead of having defaults.
What is your suggestion?
conan cache path
only allows querying the export_source, source, build, and metadata folders. It seems that the package folder, containing the final binaries, cannot be queried? Is that an oversight?Have you read the CONTRIBUTING guide?
The text was updated successfully, but these errors were encountered: