Skip to content

[Feature Request] Lower macOS build target to 10.13? #714

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

Closed
joeyballentine opened this issue Aug 24, 2022 · 2 comments · Fixed by #716
Closed

[Feature Request] Lower macOS build target to 10.13? #714

joeyballentine opened this issue Aug 24, 2022 · 2 comments · Fixed by #716

Comments

@joeyballentine
Copy link
Contributor

As you might be aware, OpenCV-python is currently built for a macOS build target of 10.15. This means that anyone on a version below 10.15 will not be able to install the prebuilt wheel and therefore pip will try to compile OpenCV on their machines.

Many macOS users are still on pre-10.15 builds as those are the last to support 32-bit applications. While I cannot personally test running a version built for 10.13, I have successfully built wheels for 10.13 on my fork of opencv-python, and the wheels pass every test.

Therefore, I am wondering if you could lower the build target to support people who are on these older versions still. I have an application that uses OpenCV, and I have received many reports from people that OpenCV fails to install as it attempts to compile locally and fails. Here is an example issue where that is the case. This issue is unfixable by me unless I were to start maintaining my own OpenCV builds with that lower build target and uploading them to pypi. I would rather not do this, and I would much rather just use the official package.

Now, if there is a reason for not using a lowered build target, please let me know. But at least based on my attempt, it seems like it should work fine.

@skvark
Copy link
Member

skvark commented Aug 25, 2022

If I remember correctly, the build target was raised to 10.15 due to some issues with external dependencies on older macOS versions (especially with Qt) and Travis (build time limits) when it was still used instead of Github Actions. Since Qt is not a dependency on macOS anymore and Travis is not used, I see no reason why 10.13 couldn't be used.

@joeyballentine
Copy link
Contributor Author

Well that's great to hear. Any idea how long it would take to get this change released, if it's approved?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants