Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi Christian:
On 2011-05-09, at 6:02 AM, Christian Lohmaier wrote:
On Mon, May 9, 2011 at 2:35 AM, Peter Teeson <peter.teeson@bell.net> wrote:
Hi Michael & *:
What discussions have there been of the idea of using Xcode, SDK 10.6

What context are you talking about?

regarding 10.6 SDK: Well, this surely will drop compatibility with
10.4 and also 10.5, so why would anyone want that?

I don't understand why you think it would drop 10.4 compatibility?
Please explain if I'm wrong but wouldn't It simply be an option?
Active Target is 10.4 or 10.6? You build what you want. 
My wife still uses my old G4 867Mhz and Tiger (10.4).
So I think having a Tiger version is fine. 
Perhaps newer capabilites would not be able to be implemented for Tiger.
But moving forward need not be constrained to Tiger. We can have both.

see
http://www.mail-archive.com/libreoffice@lists.freedesktop.org/msg09703.html
and following.

Yes I followed that at the time and understand your concerns. See above.

up and the LLVM compiler?

? What's that? Why would that be a good thing?

Apple has pretty well moved from GCC to LLVM as the standard compiler.

What order of magnitude might bethe scope of work in terms on person hours?

Supporting 10.6 SDK for building: can be done in one day - but see the
above thread please.

See my musings in the other email answer to Tor.

respect....

Peter



Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.