-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[question] Correct way to set dependency options #7148
Comments
Maybe I should move the |
Hi @Tridacnid To solve the conflict by defining |
Ok, just want to make sure I'm setting default and needed options correctly. Thanks! |
Hi! @Tridacnid , take into account that there will be only one *To be able to use these targets, #7108 has to be merged (next |
Makes sense, and the Conan errors are descriptive enough for me to quickly figure out how to resolve the problem. That upcoming functionality looks nice, I'll look into switching to use that once it's available. Thanks again! |
$ conan --version
Conan version 1.22.2
My project consumes lib1 and lib2, both of which consume boost.
ERROR: boost/1.68.0: lib1 tried to change boost/1.68.0 option header_only to False
but it was already assigned to True by lib2
For both link performance as well as only "linking what you use", I try to keep the boost project's options aligned with what's needed using a combination of header_only and the without_X options.
I thought I had set up my default_options correctly, but I clearly have something messed up.
lib1 requires specific submodules of boost, and therefore does not want the header_only option enabled. The relevant portions of lib1's conanfile look something like:
lib2's conanfile.py is simple, the relevant options look something like:
If I had to guess, lib1's conanfile is at fault. What is the correct way to override options for a dependency when you 100% need them to be set a certain way?
The text was updated successfully, but these errors were encountered: