[MacPorts] #41817: CMake @2.8.12_2: remove /sw paths from installed cmake modules

MacPorts noreply at macports.org
Sun Mar 2 09:43:14 PST 2014


#41817: CMake @2.8.12_2: remove /sw paths from installed cmake modules
----------------------+-------------------
  Reporter:  egall@…  |      Owner:  css@…
      Type:  defect   |     Status:  new
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.2.1
Resolution:           |   Keywords:
      Port:  CMake    |
----------------------+-------------------

Comment (by mojca@…):

 Please keep in mind that you also patched `Modules/FindFreetype.cmake` by
 removing `/usr/X11R6`. The arguments that you don't want to patch every
 single module file or that one should explicitly define where to take the
 module from is equally true for FreeType.

 While I agree that users should try to avoid installing Fink, I would also
 try to prevent these kind of problems from happening as long as there are
 reasonable ways to achieve this.

 See also an ugly patch in a port that I maintain
 http://trac.macports.org/browser/trunk/dports/science/geant4/files/patch-
 cmake-Modules-Geant4InterfaceOptions.cmake.4100.diff. Despite everything I
 often still need to set:
 {{{
 configure.args-append \
                     -DX11_INCLUDE_DIR=${prefix}/include \
                     -DX11_X11_INCLUDE_PATH=${prefix}/include \
                     -DX11_X11_LIB=${prefix}/lib/libX11.dylib \
                     -DX11_SM_LIB=${prefix}/lib/libSM.dylib \
                     -DX11_SM_INCLUDE_PATH=${prefix}/include \
                     -DX11_ICE_LIB=${prefix}/lib/libICE.dylib \
                     -DX11_ICE_INCLUDE_PATH=${prefix}/include \
                     -DX11_Xext_LIB=${prefix}/lib/libXext.dylib \
                     -DX11_Xpm_INCLUDE_PATH=${prefix}/include \
                     -DX11_Xpm_LIB=${prefix}/lib/libXpm.dylib \
                     -DX11_Xft_INCLUDE_PATH=${prefix}/include \
                     -DX11_Xft_LIB=${prefix}/lib/libXft.dylib
 }}}
 and I simply don't understand the point. The `configure`-based
 installation seems more reasonable in some cases.

 In my opinion there should be a way to globally set the search paths in
 CMake (and an option to prevent searching in those paths). I would try to
 talk to CMake developers to find a way to deal with these problems, but if
 we can't find a solution that suits everyone I would tend to agree with
 Eric that `/sw` should go.

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


More information about the macports-tickets mailing list