[feature] add support for per recipe config in profile
See original GitHub issueHello,
According to https://docs.conan.io/en/latest/reference/profiles.html, it is possible to define per recipe options, settings and env vars in a profile.
[settings]
zlib:compiler=clang
[env]
zlib:CC=$CLANG/clang
It we be also great if we can define config per recipe as well, something like
[conf]
*:tools.cmake.cmaketoolchain:generator=Ninja
zlib:tools.cmake.cmaketoolchain:generator=Visual Studio 16 2019
The reason is, when doing cascade build, we need to use different generators for different dependencies.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Using profiles with Compose - Docker Documentation
Using profiles with Compose. Profiles allow adjusting the Compose application model for various usages and environments by selectively enabling services.
Read more >Step 3: Creating configuration profiles and feature flags
AWS AppConfig supports the following types of configuration profiles. Feature ... (Optional) Add Attributes and attribute Constraints to the feature flag.
Read more >The roles and profiles method - Puppet
The roles and profiles method is the most reliable way to build reusable, configurable, and refactorable system configurations.
Read more >Yocto Project Reference Manual
Images: Describes the standard images that the Yocto Project supports. Features: Describes mechanisms for creating distribution, machine, and image features ...
Read more >Profile your build - Android Developers
Learn how to profile your build to help optimize build speed.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Maybe just update the documentation. Thanks.
First test:
==> Does not work
Second test:
==> It works
I seems like the order of config matters, per recipe config needs to be defined after global config.