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
PR #14194 changes the default behaviour for some of the options. Do the options affect the binary artifact id?
If I build a package without specifying the default options in the recipe using conan 2.0.7 and conan 2.0.8, will the generated binary artifact id be the same?
Have you read the CONTRIBUTING guide?
I've read the CONTRIBUTING guide
The text was updated successfully, but these errors were encountered:
Hi @alessiosacco thanks a lot for your question, great to see interest in super new features, we appreciate the feedback and questions we get regarding those as they help us to make better informed decisions!
So, you have a few questions:
Do the options affect the binary artifact id?
Yes, recipe options (As well as settings) affect the resulting package id, so that for example you don't end up with shared and static packages having the same id.
If I build a package without specifying the default options in the recipe using conan 2.0.7 and conan 2.0.8, will the generated binary artifact id be the same?
A few cases to consider:
If you do not define any options, the id's will be the same in both versions
If you defined the options, and also the configure(), config_options() & package_id() methods, the package id will be the same. Conan does not handle those methods by itself if they are already defined
If you defined the options, but did not define the methods, then yes, the resulting id might be different. This is expected. In 99.999% of cases, what Conan automatically handles is something that your recipe should already be doing, else it's a sign that something's up with it. If you have a really good reason not to let Conan handle those options (We know of some cases were some users were for example not removing the compiler for header-only libraries, for example), you can always define a the methods like:
defconfigure():
pass
to opt out the automatic handling
Let me know if this helps, else I'll be happy to answer any other question you should have!
What is your question?
PR #14194 changes the default behaviour for some of the options. Do the options affect the binary artifact id?
If I build a package without specifying the default options in the recipe using conan 2.0.7 and conan 2.0.8, will the generated binary artifact id be the same?
Have you read the CONTRIBUTING guide?
The text was updated successfully, but these errors were encountered: