On 19/08/13 11:30, Gijs Kruitbosch wrote:
Note also that this is a big 'if' - on OS X, for instance, AFAIK we
build with the 10.6 SDK on the official builds (because we still
support 10.6). Getting a 10.6 SDK on a 10.8 mac is moderately painful
(OTOH, there are real bugs that occur when building with the 10.6 SDK
but not with the 10.8 SDK - and on yet another hand, there are
probably bugs for which the inverse is true, too...)
~ Gijs
Talking about Mac OS X, I'm currently stuck on SDK matters. Here is a
link to the relevant comment:
https://bugzilla.mozilla.org/show_bug.cgi?id=868648#c53
Quote:
My past practice, using Xcode, was to use the latest SDK while
targeting the earlier supported system for our products. And it worked
as expected Objective C wise: when running on earlier systems,
unimplemented methods just returned nil. Which we took care of
checking at runtime.
In our case this would mean using 10.8 SDK and targeting 10.6.
I have no idea though how this translates in our own build system. And
maybe we have a good reason not to do so.
Markus' workaround is fine, but I'd still like to know why we're not
using 10.8 SDK.
André
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
