[MacPorts] #48288: CMake generating broken Xcode projects when using OpenCV

MacPorts noreply at macports.org
Thu Jul 9 04:11:22 PDT 2015


#48288: CMake generating broken Xcode projects when using OpenCV
-----------------------------------+--------------------------------
  Reporter:  christian.richardt@…  |      Owner:  macports-tickets@…
      Type:  defect                |     Status:  new
  Priority:  Normal                |  Milestone:
 Component:  ports                 |    Version:  2.3.3
Resolution:                        |   Keywords:
      Port:  opencv cmake          |
-----------------------------------+--------------------------------
Changes (by ryandesign@…):

 * cc: ryandesign@… (added)


Comment:

 I'm guessing the double slash is coming from the
 [browser:trunk/dports/_resources/port1.0/group/cmake-1.0.tcl at 135668:142#L139
 cmake 1.0 portgroup] which sets `-DCMAKE_OSX_SYSROOT="/"` when the sdk is
 not set (otherwise it sets it to the sdk). My recollection is that we have
 to set `CMAKE_OSX_SYSROOT` to a non-empty value, because cmake requires
 this when `MACOSX_DEPLOYMENT_TARGET` is set, which in MacPorts it always
 is. I am remembering that if we did not do this, cmake would either error
 out, or choose an SDK to use even when we had not asked for one.

 A double slash in a path should not be a problem; the OS is able to handle
 that and collapse multiple slashes down to a single one. So what exactly
 is the problem? You said `FRAMEWORK_SEARCH_PATHS =
 (//System/Library/Frameworks, );` cannot be parsed. Why is it invalid?
 What would be valid? Is the problem really the double slash at the
 beginning, or is it perhaps the comma at the end? (Apple documentation on
 `FRAMEWORK_SEARCH_PATHS` says it is a space-separated list, so the comma
 seems wrong to me.)

 I agree with you that this may be caused by one of the variants you've
 selected, because I don't see this on my system nor do I see it in our
 [http://packages.macports.org/opencv/ binary packages]. Can you narrow it
 down? I am suspicious of the way that
 [browser:trunk/dports/graphics/opencv/Portfile at 138361:247,265#L241
 opencv's tbb variant] messes with `OPENCV_LINKER_LIBS`, which none of the
 other variants do, but even if I install opencv with the tbb variant I
 don't see a reference to the frameworks directory in the places where
 you've reported seeing it.

-- 
Ticket URL: <https://trac.macports.org/ticket/48288#comment:3>
MacPorts <https://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list