[MacPorts] #27815: qt4-mac @4.7.1 Missing symbols - build failure

[MacPorts]

#27815: qt4-mac @4.7.1 Missing symbols - build failure
---------------------------------------+------------------------------------
  Reporter:  okmacports@…              |       Owner:  michaelld@…           
      Type:  defect                    |      Status:  closed                
  Priority:  Normal                    |   Milestone:                        
 Component:  ports                     |     Version:  1.9.2                 
Resolution:  fixed                     |    Keywords:                        
      Port:  qt4-mac                   |  
---------------------------------------+------------------------------------

Comment(by okmacports@…):

 Replying to [comment:8 michaelld@…]:
 > Should be fixed in r74982.  Do a "sudo port selfupdate" to get the
 changes, then try to build anew (again; sorry).  I'm going to go ahead and
 close this ticket as fixed, but please do reopen if my patch doesn't work
 for this ticket's specific issue.

 I am happy to report that yes, it now builds, BUT ...

 There is a fundamental problem, I think, with how it searches for the SDK
 directory.

 In order for something like, say, cairo to build properly, the
 developer_dir variable in the macports.conf file has to be set to
 /Developer, where it then finds /Developer/Applications/Xcode.app.

 BUT then it won't find the MacOSX SDKs. Alternatively, if I set
 developer_dir to /Developer/Platforms/MacOSX.platform/Developer, then
 qt4-mac finds the SDKs but cairo can't find Xcode.app.

 As developer_dir is documented as defaulting to the output of `xcode-
 select` (in reality, `xcode-select -print-path`) I think it's best to
 leave that alone. Perhaps the best solution is to create another
 macports.conf variable, sdk_dir, which defaults to:

 {{{
 xcodebuild -version -sdk |grep -m1 '^Path: .*MacOSX.*SDKs.*' |sed
 's,^Path: \(.*\)/[^/]*$,\1,'

 which is to say,
 /Developer/Platforms/MacOSX.platform/Developer for cross-platform 10.6+
 developers and (I think)
 /Developer for the older structure
 }}}

 For the time being, I have set developer_dir to /Developer and created a
 symlink (ugh) from /Developer/SDKs to
 /Developer/Platforms/MacOSX.platform/Developer/SDKs. I hope that will be a
 very temporary workaround.

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