[MPlayer-dev-eng] [REPOST] [PATCH] Mac OS X fixes + Darwin AltiVec detection

[Dan Christiansen]

On Thursday, April 3, 2003, at 03:37 PM, Alex Beregszaszi wrote:

> Hi,
>
> My mailing system was broken.

:)

> Is the -framework Carbon needed? And what about CoreFoundation?
> Btw, i don't even think that these -frameworks are required, becouse
> it's a objective-c only switch, and mplayer hasn't got any objective-c
> sources.

Yes, I believe it's needed since QuickTime depends on it. IIRC, I also 
had to include Carbon since some of the items present in QuickTime for 
Windows are part of Carbon on Mac OS X. (Apple ported a small subset of 
Mac OS to Windows along with QuickTime.) Another reason for having it 
is that simply checking for QuickTime could lead to false positives. 
AFAIK, no CoreFoundation API is used within MPlayer, so it's irrelevant.

About the -framework switch; no it isn't Objective-C only. A framework 
is basically a wrapper for a library which ensures that the library, 
it's headers and any documentation is in one package enabling easy 
installation and removal. It's roughly equivalent to -l, and that's 
also why it's passed when linking rather than compiling.

In the very early pre-release days of Mac OS X, Apple distributed some 
libraries as frameworks. Since this would require people to use 
different compiler flags on Mac OS X, they no longer recommend doing 
this.

 From "man ld" on my mac:
>>        -framework name[,suffix]
>>               Specifies a framework to link  against.  Frameworks
>>               are  dynamic  shared libraries, but they are stored
>>               in  different  locations,  and  therefore  must  be
>>               searched for differently. When this option is spec-
>>               ified,  ld  searches  for  framework   `name.frame-
>>               work/name'  first in any directories specified with
>>               the -F  option,  then  in  the  standard  framework
>>               directories        /Library/Frameworks,       /Net-
>>               work/Library/Frameworks, and /System/Library/Frame-
>>               works.   The  placement of the -framework option is
>>               significant, as it  determines  when  and  how  the
>>               framework  is  searched.  If the optional suffix is
>>               specified the framework is first searched  for  the
>>               name with the suffix and then without.
>>
>>        -Fdir  Add  dir  to  the  list  of directories in which to
>>               search for frameworks.  Directories specified  with
>>               -F  are  searched  before  the  standard  framework
>>               directories.

> And about the first part: dunno, originally there was darwin+altivec
> autodetection, will have a deeper look at it.
>
> Please don't commit this, i'm going to do it after cleaning the issues
> mentioned upper.