-
Notifications
You must be signed in to change notification settings - Fork 993
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] How to make a single tool package for debug and release builds in Conan 2.0 #14894
Comments
My workaround here was just to use cmake via command line...is that the recommended approach? |
What I did is exclude the def package_id(self):
self.info.settings.rm_safe("build_type") Not sure if that's the recommended approach though. There's also some documentation about this: https://docs.conan.io/2/tutorial/creating_packages/other_types_of_packages/tool_requires_packages.html#removing-settings-in-package-id |
Hi @rconde01 Thanks for your question.
For So a perfectly valid and very simple strategy is to do nothing, and just rely on the In any case, I think the use case that you are exposing should be easier to implement with the
|
Closing as responded by the last comment. |
What is your question?
I have a package which builds a tool. I always want a release build of this tool despite what the consumer is using. I am using
CMakeToolchain
andCMake
classes. I think I can forceCMAKE_BUILD_TYPE
inCMakeToolchain
, butCMake
is insisting the package needs abuild_type
setting - which would mean I need to duplicate the package for debug/release. Is there a way to accomplish what I want?Have you read the CONTRIBUTING guide?
The text was updated successfully, but these errors were encountered: