-
Notifications
You must be signed in to change notification settings - Fork 994
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] conan2: unnecessary build requirements #15657
Comments
in profile I have overriden default build requirement with my own version. Example:
|
for some reason this behavior is affected by "--build=missing" conanfile.py
profile:
without --build=missing
with --build=missing
|
Conan 2 doesn't install Downloading the recipes is very fast, it shouldn't have any big impact on the performance. The case for
As a hint, Conan 2.0 has provided the |
So with --build=missing the only way to not build build_requirements is to upload them to remote? Even if I used them only once for building package that was uploaded to remote? As for generate\deploy - this conanfile.py is generated on the fly multiple times during CMake generation with different sets of packages and I always deploy dlls so there is probably no difference. |
Yes, uploading the binaries used to build other packages to the server is a very good practice regarding reproducibility and traceability, not to say that it is very likely that it can be reused later, to build the next openssl version, that might have exactly the same build-requires, and it won't need to rebuild it again. |
The strange thing is that I don't have binaries for b2/4.10.1 on my remote but with the same approach conan skips building b2 while successfully downloading binaries for boost. |
After looking at build requirements that downloaded only recipe:
build requirements that downloaded recipe and were built from source:
Maybe build type in settings somehow affects this? Or package_type? Second list doesn't use any compiler information. |
just checked - if I do the same with nasm that is also used in openssl - nasm isn't being built
profile
|
Ok, thanks for the extensive report and details. I think there is something in the binary compatibility management that is affecting, and it could only be affecting some packages, like those that define |
I have finally managed to reproduce this, thanks very much for the feedback and details! It happens when there are multiple repeated |
#15885 merged, this will be in next 2.2 |
What is your question?
Hi! I'm generating conanfile.py from CMake in the form of:
I've noticed that conan2 installs build requirements even when already built package has been downloaded from remote or is already present in local cache. Is there a way to not download build requirements in this case? I think that conan 1.X didn't have this behavior.
Have you read the CONTRIBUTING guide?
The text was updated successfully, but these errors were encountered: