Conversation
|
@chrisballinger Thank you for contribution! /cc @komakai Could you please check |
|
@vpisarev Please take a look. |
|
@chrisballinger thanks for this. I don't have much insight into Python2 -> Python3 porting, but I have run builds with and without your changes and can confirm that the generated Objective-C sources was the same in both cases. (Note: had to run |
|
@komakai Ah ideally I'd want to remove a dependency on any pip packages, I didn't realize |
2754000 to
fb10a88
Compare
fb10a88 to
e3b2ae5
Compare
|
Alrighty I think I was able to remove the @komakai Can you share with me an example manual test invocation of the |
|
BTW, Used parameters of this script are visible in build logs on CI:
|
This reverts commit 0bc101f.
|
Thanks! I reverted the last |
Xcode 12 and Python 2/3 fixes * Fix compilation issues using Xcode 12 on macOS Catalina * Fix macOS scripts to work on Python 2 or 3 * Fix additional issues with Python 3 * Fix additional Python 2/3 issue * Fix another Python 2/3 issue * Remove dependency on builtins module
Pull Request Readiness Checklist
This pull request resolves a couple issues when building OpenCV using Xcode 12 on macOS Catalina:
IPHONEOS_DEPLOYMENT_TARGETnow defaults to9.0because that is the minimum version allowed by Xcode 12modules/objc/generator/gen_objc.pyand platform build scripts have been ported to Python 2/3 usingfuturizeas well as a few manual fixes regarding utf8/bytes handling, because it would fail if your#!/usr/bin/env pythoncheck evaluated to apython3binary. Another alternative I considered was using#!/usr/bin/env python2, but I'm not sure how much longer Python 2 will be supported.Patch to opencv_extra has the same branch name.