-
Notifications
You must be signed in to change notification settings - Fork 1k
Feature/profile contexts #18383
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
base: develop2
Are you sure you want to change the base?
Feature/profile contexts #18383
Conversation
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.
So much passing info down, but I can see that this is in fact useful
c.run("create . -s os=Windows -s arch=armv8") | ||
|
||
# This will pick the Linux+x86 package binary | ||
c.run("list *:* --filter-profile=base") |
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.
Nice idea to test this, I think we should make sure that users understand that the context would have 3 potential values in the docs
I tested {% if context == "host" %}
[settings]
build_type=MinSizeRel
os=baremetal
arch=cortex-m3
libc=custom
[options]
*:platform={{ platform }}
{% endif %}
{% if context == "build" %}
[options]
arm-gnu-toolchain/*:fat_lto=False
{% include "default" %}
{% endif %} and my build command was: VERBOSE=1 conan build demos -pr:a conan/profiles/v1/stm32f103c8 -pr arm-gcc-12.3 I was checking to see if my toolchain package would recognize the option |
Changelog: Feature: Add
context
variable to profile jinja2 rendering (can be "build", "host" andNone
).Docs: https://github.com/conan-io/docs/pull/XXXX
Close #18375