-
Notifications
You must be signed in to change notification settings - Fork 365
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PkgConfigDeps][MesonToolchain] Added build context folder mechanism #3640
[PkgConfigDeps][MesonToolchain] Added build context folder mechanism #3640
Conversation
@@ -111,6 +111,8 @@ you can activate it using the **build_context_activated** attribute: | |||
build_context_suffix | |||
^^^^^^^^^^^^^^^^^^^^ | |||
|
|||
*DEPRECATED: use build_context_folder attribute instead* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this true for autotools
projects too? Or only for Meson
? I think only Meson has the capability of specifying a folder for the build-requires?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
MesonToolchain
has the build.pkg_config_path
variable, but I did not figure out how to do that in Autotools. Any ideas?
build_context_suffix | ||
^^^^^^^^^^^^^^^^^^^^ | ||
|
||
*DEPRECATED: use build_context_folder attribute instead* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is still not very clear that the deprecation of this and the recommendation to use build_context_suffix
is the way to go also for autotools. If it is not, maybe we should recommend this for Meson only?
Maybe we need to understand the potential autotools usages of the build_context_suffix
and build_context_folder
Docs for conan-io/conan#15813. (MesonToolchain explanation is covered by the docstring)