Re: Xcode 4 -- support of 10.4 / 10.5, PowerPC, ...
Re: Xcode 4 -- support of 10.4 / 10.5, PowerPC, ...
- Subject: Re: Xcode 4 -- support of 10.4 / 10.5, PowerPC, ...
- From: Joar Wingfors <email@hidden>
- Date: Sat, 12 Mar 2011 21:30:48 -0800
Hello Ruslan,
On 12 mar 2011, at 00.57, Ruslan Zasukhin wrote:
> * in short: for now we also have decide that jump into XCODE 4 is good only
> For iOS developers, but we are a Valentina DB team,
> We develop in C++ ...
Xcode 4 ships with the LLVM compiler 2.0 that provides much improved support for C++ in all parts of the IDE. Indexing, code completion, compile performance, etc. Have you tried it? We absolutely intend to provide first class support for C++ in Xcode. We might not be all there yet, but we should be pretty close, and certainly way better than Xcode 3.
> Does Apple says that if we go to modern cool Xcode4,
> Then we must drop support of all PowerPC macs,
> And drop support of MAC OS 10.4 and 10.5 ?
It is true that Xcode 4 doesn't support developing for Mac oS X 10.5 and earlier. If you need to target 10.5 (and I understand that many of you do) you should continue to use Xcode 3.2 for that purpose.
> But I have see list of dropped features, and some items looks strange.
>
> * no way to complex single file.
>
> wow. This for 10-15 years feature of CodeWarrior and than Xcode.
> Visual many years did not have it and was blamed.
> Now Visual have it, but Xcode tema have decide go down ... Sense?
Given that the fix-it feature of Xcode 4 provides "live" warnings & errors as you type, why do you feel that you need single file compile?
> * no way pre-process file
>
> all same - for years was feature in CW and X4.
> One per month I have used it as C++ developer. And say thanks ...
> Visual do not have this up to now...
> Visual allow it in hard way ... Set prefs for file, get precompiled
> in some hard to find folder ...
>
> And Xcode team have drop this ... Sense ?
This feature is indeed missing in Xcode 4. I can't comment on our future directions, so that's about as much I can say about that. For now, you can always get to the preprocessed output by copying the compiler invocation for the file in question from the build log, adding the directive to keep the preprocessed intermediary state, and then executing it manually on the command line. I understand that's not as convenient as having this feature exposed in the IDE of course.
Best,
j o a r
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden