workflow: auto-resolve conanfile path from config.yml#71
Closed
workflow: auto-resolve conanfile path from config.yml#71
Conversation
Instead of requiring manual conanfile_path input (defaulting to all/conanfile.py), automatically resolve the correct folder from each package's config.yml based on package name and version. This ensures packages with non-standard folders (openssl, cmake, b2, onetbb, folly, etc.) are built with the correct recipe without relying on the user to remember the right path. The conanfile_path input is kept as an optional override. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
sparknack
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Instead of requiring manual conanfile_path input (defaulting to all/conanfile.py), automatically resolve the correct folder from each package's config.yml based on package name and version.
This ensures packages with non-standard folders (openssl, cmake, b2, onetbb, folly, etc.) are built with the correct recipe without relying on the user to remember the right path.
The conanfile_path input is kept as an optional override.