-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
Build a headless opencv version #337
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe:
|
@conda-forge-admin please rerender |
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
26b53c8
to
e8d6d30
Compare
This is mostly really useful for those that want to start testing with qt6 |
@conda-forge/opencv thoughts on maintainability are appreciated. |
@conda-forge-admin please rerender |
Sorry it seems like there is still some work to do on windows. |
@conda-forge-admin please rerender |
1 similar comment
@conda-forge-admin please rerender |
- liblapacke | ||
- liblapack | ||
- libcblas | ||
- freetype | ||
- glib # [unix] | ||
- glib |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think that glib is actually required:
conda-forge/conda-forge.github.io#1880
# Prioritize qt5 for noq over none and over qt6 | ||
|
||
{% if qt_version == "5" %} | ||
{% set build = build + 400 %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we use track_features
instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The mamba way? that wasn't too popular in pytorch / tensorflow (i forget which). this is just "simpler" and easier to understand.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I remembered that @xhochy recently recommended using it: conda-forge/staged-recipes#21247
@@ -96,21 +104,17 @@ requirements: | |||
# no quesitons about the license of the resulting opencv | |||
# binary | |||
- ffmpeg {{ ffmpeg }}=lgpl_* | |||
- qt-main # [not osx and not ppc64le] | |||
- qt-main # [qt_version == 5] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would != none
be better, considering our move to qt6 at some point?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Honestly, my branch is called qt6
because i tried to get qt6 to work. I just couldn't, so i kinda "gave up" and reverted to this simpler one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. All good then :)
I'm not a maintainer, but overall LGTM, just some minor suggestions. |
@conda-forge-admin please rerender |
…nda-forge-pinning 2023.01.23.01.26.33
@conda-forge-admin please rerender |
…nda-forge-pinning 2023.01.23.01.26.33
@conda-forge-admin please rerender |
…nda-forge-pinning 2023.01.23.01.26.33
I'm not convinced this is the right approach due to increased maintenance burden. |
@hmaarrfk What is the recommended approach for |
is my only recommendation. I'm not sure. I feel like The main issue with pypi is that one package may depend on This merge request (as it is) wouldn't make pypi find a locally installed version of I would accept updates to this feedstock that make it look like a Perhaps you can be inspired by: https://github.com/conda-forge/opencv-feedstock/blob/main/recipe/install_pip_metadata.patch I would ask that you add alot of |
Hi @hmaarrfk, thank you for this piece of work! I might be able to help with packaging the equivalent of Is there a lot of work left? Would you be able to estimate the time it would take to finish it? Can I contribute to your efforts? |
on the coding side, the answer is that it is "done". the question I have is:
if you have ideas on how to deliver it to the wider audience I am glad to hear it. personally, I see this request as quite niche, and those that require it can likely rebuild opencv using azure's free agents and upload the package to their channel. the package would be called |
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)