Which Xcode?

[René JV Bertin]

I already adapted Xc 3.2 .pbcompspec files to have Macport's gcc48 and clang 3.4 in the IDE, as well as Apple 's Clang 3 from Xc 4. 
The SDKs might be more challenging.

R

On 23 Nov 2014, at 14:27, Michael Crawford <mdcrawford at gmail.com> wrote:

> Apple has not documented any way to plug in compilers other than those
> that come with Xcode.  That doesn't mean that one cannot do so, just
> that Apple won't tell you how.
> 
> However - while it would be some work - you could write an external
> "compiler" that plugs into CodeWarrior.  That would just be a wrapper
> around the clang command-line tool, as well as the various
> configuration dialogs.
> 
> The current FreeScale CodeWarrior only runs on Windows, I think, but
> you could write a clang plugin for CodeWarrior 8 or 9.
> 
> Am I correct that CodeWarrior Pro 9 for OS X was free as in beer?
> 
> I have CodeWarrior Pro 8 for both Windows and Mac.  It's quite nice.
> Michael David Crawford
> mdcrawford at gmail.com
> http://www.warplife.com/mdc/
> 
>   Available for Software Development in the Portland, Oregon Metropolitan
> Area.
> 
> 
> On Sun, Nov 23, 2014 at 4:51 AM, René JV Bertin <rjvbertin at gmail.com> wrote:
>> I wonder to what extent Xcode 3.2.6 can be configured to use new clang and the latest SDKs. That's an IDE concept I still prefer: individual editor windows, a separate project window etc. I really don't get that fashion of monolithic interfaces that block everything behind them and make it complicated to do copy/pasting among documents.
>> 
>> R
>> 
>> On 23 Nov 2014, at 09:44, Michael Crawford <mdcrawford at gmail.com> wrote:
>> 
>>> Xcode doesn't really do anything that you couldn't do with clang,
>>> llvm, gnu make and your choice of text editor.
>>> 
>>> The best I've ever been able to say about Xcode is that I found it
>>> barely tolerable, now I regard using it as just like pounding nails
>>> with my fists.
>>> 
>>> This is not at all to say I don't like Integrated Development
>>> Environments.  I like them just fine - ThinkC, Symantec C and
>>> Metrowerks CodeWarrior all suited me just fine.  It's that I regard
>>> Xcode as quite poorly designed.
>>> 
>>> While I haven't actually done so yet, sometime soon I'm going to write
>>> a Makefile to build my iPhone App Warp Life
>>> (http://www.warplife.com/life/).  I'm planning to release the source
>>> as Free Software.  That source release isn't going to come with an
>>> Xcode project, because I have grown so weary of new versions of Xcode
>>> breaking stuff that used to work well.
>>> Michael David Crawford
>>> mdcrawford at gmail.com
>>> http://www.warplife.com/mdc/
>>> 
>>>  Available for Software Development in the Portland, Oregon Metropolitan
>>> Area.
>>> 
>>> 
>>> On Sat, Nov 22, 2014 at 11:23 PM, René JV Bertin <rjvbertin at gmail.com> wrote:
>>>>> If you have concerns about problems in Xcode 6.1, could you be more specific?
>>>> 
>>>> I suppose he may be referring to the reviews on the Store (I checked several national stores, the reviews all agree that this version is buggy and crashy)
>>>> 
>>>> _______________________________________________
>>>> macports-users mailing list
>>>> macports-users at lists.macosforge.org
>>>> https://lists.macosforge.org/mailman/listinfo/macports-users
>>> _______________________________________________
>>> macports-users mailing list
>>> macports-users at lists.macosforge.org
>>> https://lists.macosforge.org/mailman/listinfo/macports-users
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macports-users
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users