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: Ruslan Zasukhin <email@hidden>
- Date: Sun, 13 Mar 2011 11:09:16 +0200
- Thread-topic: Xcode 4 -- support of 10.4 / 10.5, PowerPC, ...
On 3/13/11 7:30 AM, "Joar Wingfors" <email@hidden> wrote:
Hi Joar,
> 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.
Yes, and new Debuger for C++ also
This is why I was so in hope to XCODE 10.4 last 6 months...
So far I have try compile only one our project ... Yes looks to be faster,
But all yet issues with Xcode prevent us from fast switch to X4...
For now I read all new docs about X4.
Better read all docs then ask :-)
So I will be back yet of course asap.
Old debuger was not able correctly handle RTTI in complex inheritance
classes, and when we use a lots interfaces (ala-COM model).
So very interesting to see how new debugger works here.
old dead CW in last versions did this job nice.
Visual also do it nice far ago.
>> 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.
Ok.
And I have to think, that we will continue yet few months with 10.3
To produce 4.9.x bug fix builds of Valentina
And 5.0 we may really drop 10.4 and 10.5 and PPC ...
Next Sept - Dec
>> * 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?
May be, may be ... We should try that
Just one nasty bug in up to XCODE 3.2 was, that if I do change in some top
header .h, e.g. Change constant value, then Xcode (or GCC) was blind to see
that change and did not self recompile related .cpp
Visual 2005 never did have such trouble.
Visual 2010 guys say also have start glitch in this area...
So only was 2 ways:
A) recompile one file
B) trash build folder(s) and recompile all from scratch
>> * 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.
Yes this is not convenient...
Please return back this nice old good feature. :-)
--
Best regards,
Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc
Valentina - Joining Worlds of Information
http://www.paradigmasoft.com
[I feel the need: the need for speed]
_______________________________________________
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