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
Use different build type values to search required dependencies (requires
attribute)
#4097
Comments
I think you could do it with per-package settings: $ conan create ./conanfile.py TSI/28.0.0@rcs/testing --profile pc_x86_ubuntu16_5.4.0 -s build_type=Release -s TSI:build_type=Debug This is possible, but just to make sure and for other readers, it is something that might fail because of ABI compatibility. There is no guarantee that the ABI between Debug and Release packages in C++ is maintained, so the final application might fail to link, or fail at runtime. In Windows/VS it typically refuses to link, mainly to different in the runtime MD/MDd. In Linux it normally works. Please tell me if the above works for your case. Thanks! |
Oups I didn't see your reply until now 8-) Ok, this is cool. Can I use this syntax (I mean |
Yes, yes, you can also use it in profiles:
This should work with your Please try the above and tell me, thanks! |
Thanks for this detailed answer. Best wishes for the festive season :-) |
Thanks to you for following up. Best wishes to you too! :) :) :) |
Here is recipe that I use to create packages this way:
I use the
-s build_type=Debug
to tell conan to consider thatTSI/28.0.0@rcs/testing
is of build type.The problem here is that this command searches for the required Artefacts (POCO, ...) using the
build_type
that I passed. In this caseDebug
, it therefore is not finding my dependencies.But what if I want to use
Release
artefact to build my Debug version ofTSI
?Is there a way to set the
TSI
build_type to Debug and still let conan search dependencies without taking this criteria into account. Ending up with thisI use conan 1.9.2 on Linux:x86_64 (Ubuntu 16).
--- conanfile.py ------------------------------------
To help us debug your issue please explain:
The text was updated successfully, but these errors were encountered: