Bug 89412

Summary: PulseAudio cross compilation for Mac OS X fails due to problems with configure.ac
Product: PulseAudio Reporter: Peter ├ůstrand <astrand>
Component: build-systemAssignee: pulseaudio-bugs
Status: RESOLVED MOVED QA Contact: pulseaudio-bugs
Severity: normal    
Priority: medium CC: lennart
Version: unspecified   
Hardware: Other   
OS: All   
i915 platform: i915 features:
Attachments: Fix OS X configure for Mac OS X

Description Peter ├ůstrand 2015-03-03 14:10:06 UTC
Created attachment 113955 [details]
Fix OS X configure for Mac OS X

There are some issues with configure.ac which makes the build fail when cross compiling for Mac OS X:

* The section #### Mac OSX specific stuff ##### comes very late; after several checks for OS S specific things such as CoreServices and CoreAudio. Obviously, fundamental things such as mac-version-min and sysroot must be setup before trying such tests. The entire section should be moved more to the top. 

* The section that checks for CoreServices has two problems: 1) It checks for FlatCarbon/CoreServices.h. AFAIK, FlatCarbon is a very old concept designed for compatibility with pre-OS X Mac OS. Since we require OS X 10.5, I see no point in checking for the FlatCarbon version. 2) There's an hardcoded path to /System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h. This is the wrong way to do it: The path should not be hardcoded, and the "CoreServices.framework" should not be specified. 

The attached patch should solve both problems. Tested with GCC 4.6.4 targeting Mac OS X 10.6.
Comment 1 GitLab Migration User 2018-07-30 10:13:37 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/283.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.