[pulseaudio-tickets] [Bug 55152] New: Apple CoreService Framework configure check uses hard-coded SDK path

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=55152

             Bug #: 55152
           Summary: Apple CoreService Framework configure check uses
                    hard-coded SDK path
    Classification: Unclassified
           Product: PulseAudio
           Version: unspecified
          Platform: All
        OS/Version: Mac OS X (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: build-system
        AssignedTo: pulseaudio-bugs at lists.freedesktop.org
        ReportedBy: adman.com at gmail.com
         QAContact: pulseaudio-bugs at lists.freedesktop.org
                CC: lennart at poettering.net


Recent Xcode versions place CoreServices.h header files within the Xcode
application bundle itself rather than /Developer, as such hardcoding the path
to /Developer/Headers/FlatCarbon/CoreServices.h in configure.ac is not suitable
for those situations. 

The Xcode prefix can be found from the output of `xcode-select -print-path`
(for Xcode 4.3+ installations, and where the path has been properly set up by
the user), however if that does not exist a set of cascading fallbacks is
recommended - then try /Developer if there are files in /Developer/usr/bin;
then /Applications/Xcode.app/Contents/Developer, in case xcode-select is broken
but Xcode is installed. The SDK path is within the Xcode prefix found above.
Also available is `xcodebuild -version -sdk macosx$(sw_vers -productVersion |
grep -o '[0-9]*\.[0-9]*') Path` command which directly gives the SDK Path.
A patch to fix this check should ideally also be compatible with the
--with-mac-sysroot command to manually override the SDK path.

An example of where the headers are located on my machine is
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.7.sdk/Developer/Headers/FlatCarbon

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.
You are the assignee for the bug.