opencv3/opencv4: eliminate portfile duplication via subports; simplify via portgroups; streamline python binding generation
— at Version 14
Now that the two OpenCV-related ports have been brought up to parity, there are very few differences between them. Eliminate the portfile duplication, via subports.
Other notable cleanup that will be tackled during the reconciliation:
- Universal use of
github
portgroup. Currently used for opencv4, but not for opencv3.
- Adopt
cmake
portgroup, to reduce number of CMake flags needed.
- If supported by OpenCV, streamline Python binding generation: Do so from the built libs, rather than rebuilding entire library.
Change History (14)
Description: |
modified (diff)
|
Description: |
modified (diff)
|
Description: |
modified (diff)
|
Description: |
modified (diff)
|
Summary: |
opencv/opencv4: eliminate portfile duplication, via subport →
opencv/opencv4: eliminate portfile duplication, via subports
|
Description: |
modified (diff)
|
Port: |
opencv3 added; opencv removed
|
Summary: |
opencv/opencv4: eliminate portfile duplication, via subports →
opencv3/opencv4: eliminate portfile duplication via subports; simplify via portgroups;
|
Description: |
modified (diff)
|
Summary: |
opencv3/opencv4: eliminate portfile duplication via subports; simplify via portgroups; →
opencv3/opencv4: eliminate portfile duplication via subports; simplify via portgroups; streamline python binding generation
|
This will be done in phases, coordinated with reinstatement of OpenCV 2 port (issue:49670):
opencv3
, segregated like opencv4. Also include initial changes, supporting later conversion to subport.opencv
, to useopencv3
. And update portopencv
to be a stub port, withreplaced_by opencv3
, etc.opencv2
, using same segregation strategy, etc.opencv
port, with three subports. This step may be combined with previous.Thoughts/feedback welcome, as always.