Details
-
User Story
-
Resolution: Out of scope
-
P2: Important
-
None
-
6.0.1
Description
The conan recipes should set build_policy to "always". This elevates the user from having to always run conan install --build.
From the documentation
With the build_policy attribute in the conanfile.py the package creator can change the default Conan’s build behavior. The allowed build_policy values are:
missing: If no binary package is found, Conan will build it without the need to invoke Conan install with --build missing option.
[...]These build policies are especially useful if the package creator doesn’t want to provide binary package.
Some comment on the use of build_policy for these purposes: https://github.com/conan-io/conan/issues/6655
The use cases are for example: a driver, that needs to be built from sources always in the target machine. Only the recipe is uploaded, but it is a bit annoying to always fail when users do install them (maybe even transitively, they are not aware of this driver).
Attachments
Issue Links
- is required for
-
QTBUG-88314 Support releasing through Conan
- Closed
- relates to
-
QTCREATORBUG-25275 Conan: Support different build policies for install build step
- Withdrawn