[MacPorts] #20199: qt4-mac fails to build when conflicting ports are active

MacPorts noreply at macports.org
Fri Jul 2 08:03:52 PDT 2010


#20199: qt4-mac fails to build when conflicting ports are active
-----------------------------------+----------------------------------------
  Reporter:  jwhowse4@…            |       Owner:  michaelld@…           
      Type:  defect                |      Status:  reopened              
  Priority:  Normal                |   Milestone:                        
 Component:  ports                 |     Version:  1.7.1                 
Resolution:                        |    Keywords:                        
      Port:  qt4-mac               |  
-----------------------------------+----------------------------------------

Comment(by mcalhoun@…):

 Replying to [comment:84 michaelld@…]:
 > Update on this ticket:  There is no "truly optimal" solution for this
 issue without tweaking the `#include`s themselves in the Qt source.
 Without tweaking the source: Putting MacPorts paths first for searching
 will find the correct libraries and headers, but will result in the
 conflicts already found.  Putting them last will resolve the conflicts --
 I've verified that yesterday; took quite a bit of hacking to get all the
 paths last, but it does work -- but no longer uses certain MacPorts-
 provided libraries and headers.

 This may be a silly idea, but could we put the MacPorts paths first (no
 patching the source) but just for the libraries we need (thereby avoiding
 conflicts)?[[BR]]
 For example, instead of -I${prefix}/include, we use something like (for
 zlib) -I${zlib_loc}/${prefix}/include, where ${zlib_loc} is found from the
 output[[BR]]
 of port location zlib.

-- 
Ticket URL: <http://trac.macports.org/ticket/20199#comment:85>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list