Hello Gabriel,

Some questions and comments:

What kind of hardware does your Mac OS X 10.5 user have (i386 / ppc)?
Which version of Xcode are you using? Note that 3.2.6 dropped PPC support.

Check your binary to verify that it contains the architectures that you expect:

$ file /path/to/ArtSaver.saver/Contents/MacOS/ArtSaver 
/path/to/ArtSaver.saver/Contents/MacOS/ArtSaver: Mach-O universal binary with 2 
architectures
/path/to/ArtSaver.saver/Contents/MacOS/ArtSaver (for architecture i386):        
Mach-O bundle i386
/path/to/ArtSaver.saver/Contents/MacOS/ArtSaver (for architecture ppc7400):     
Mach-O bundle ppc

Finally, you should try the static analyzer, there are a couple of memory leaks 
that it could locate for you.

j o a r


On 31 mar 2011, at 18.58, Gabriel Zachmann wrote:

> I am really beginning to pull my hair, because it seems that I am incapable 
> of compiling my screensaver for 10.5.
> 
> I've got one user who says that he can't install my screensaver under 10.5.
> I have tried a number of different settings in my project settings, to no 
> avail.
> Unfortunately, I don't have a machine with 10.5 at hand.
> So I don't know whether it's a general problem with 10.5 I'm having, or it's 
> just this one user.
> 
> So I was wondering, if one of you who still has got a 10.5 machine could just 
> try it out.
> You can grab the complete project here: 
> http://zach.in.tu-clausthal.de/tmp/ArtSaver.zip
> 
> Maybe you can look at my project settings, if I've done something wrong. 
> (It's the configuration "Release 10.5")
> Or maybe you can compile it (preferably under 10.6) and try to run it on 10.5.
> 
> I'd appreciate that really really very much.

_______________________________________________

Cocoa-dev mailing list ([email protected])

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to