[MPlayer-dev-eng] [PATCH] Mac OS X fixes

Dan Christiansen danchr at daimi.au.dk
Fri Mar 28 17:14:30 CET 2003


On Thursday, March 27, 2003, at 07:43 PM, Alex Beregszaszi wrote:

> Hi,
>
> I go further, i don't even see the sense of this.
> The -framework stuff isn't specific to objective-c? If yes, it doesn't
> make sense to put it into mplayer, becouse there aren't any .m files.
>
> (Anyway, if I'm false, the -x objective-c doesn't seem make sense
> either)

The idea behind the change from -ObjC to -x objective-c was that -ObjC 
is specific to Apple GCC and would thus cause the test to fail 
needlessly on a system where someone had compiled there own version of 
GCC.

The original idea was to have as much as possible in the test so that 
it would fail on any other system than Mac OS X, but coming to think of 
it, it seems better to simply test for what is used. The new patch 
reflects this.

I noticed that configure didn't seem to detect the presence of an 
AltiVec unit on Darwin. I don't have a G4 myself, so I can't test this, 
but attached below is a small patch to check for it using sysctl. Does 
MPlayer support runtime CPU detection on the PPC as well?

- Dan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: darwin_cpudetect.diff
Type: application/octet-stream
Size: 581 bytes
Desc: not available
URL: <http://lists.mplayerhq.hu/pipermail/mplayer-dev-eng/attachments/20030328/3c2d4e3e/attachment.obj>
-------------- next part --------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: minor_fix.diff
Type: application/octet-stream
Size: 2625 bytes
Desc: not available
URL: <http://lists.mplayerhq.hu/pipermail/mplayer-dev-eng/attachments/20030328/3c2d4e3e/attachment-0001.obj>


More information about the MPlayer-dev-eng mailing list