Since the new versions do include a 10.6 SDK, one option is to use the 10.6 SDK with a deployment target of 10.5. I tried this and with bug 674440 fixed I was able to, on 10.7 with Xcode 4.1, build a copy of firefox that worked on 10.5. I have uploaded the dmg to
http://people.mozilla.org/~respindola/firefox-8.0a1.en-US.mac.dmg
I opened bug 674655 for the actual change (using the 10.6 sdk). One dependency is that, if we are to use the 10.6 sdks, we have to move our build to (at least) 10.6 machines. Currently only our debug builds are done on 10.5 and I opened bug 674647 to track the options we have to move them to 10.6.
Does anyone have a dependency on the 10.5 sdk that I might have missed?
Cheers,
Rafael
I'm not aware of any ... but that doesn't mean that none exist.
I suggest we try this change out on the trunk for a month or two,
before we start doing this on the branches.
On Jul 28, 9:08 pm, Rafael Ávila de Espíndola <respind...@mozilla.com>
wrote:
Thanks,
Christian
> _______________________________________________
> dev-platform mailing list
> dev-pl...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
My original plan was to this on m-c and current development branches. As
we drop support for the old branches, the support for the 10.5 sdk would
go with it.
How much infrastructure do we normally keep around for the old branches?
I am sure we don't have ppc machines as an option on try for example.
> Thanks,
> Christian
>
Cheers,
Rafael
Not much, and it is generally a wasteland:
http://tinderbox.mozilla.org/showbuilds.cgi?tree=GeriatricMachines