ts-7000
[Top] [All Lists]

[ts-7000] Re: Cross compiler on Mac OSX - finally!

To:
Subject: [ts-7000] Re: Cross compiler on Mac OSX - finally!
From: "tachion0niohcat" <>
Date: Tue, 29 Sep 2009 19:30:20 -0000
Just wondering the following, I haven't tried:

The new XCode with the IPhone SDK comes with an ARM cross compiler build in, 
since the IPhone is ARM based.

Is that of any use for cross compiling ARM code other than for the IPhone (and 
Ipod I guess) ? 

Maybe, at the least, you have the compiler installed already and all you need 
to do is tweak the environment?

--- In  "" <> wrote:
>
> Any news on getting XCode to cross compile?
> 
> Thanks
> Ciao
> Roberto
> 
> --- In  "bburtan65" <bburtan65@> wrote:
> >
> > --- In  "doogul" <macg3@> wrote:
> > >
> > > I wrote those directions and posted them a while back in response to 
> > > someone asking about how to make an OS X toolchain. Unfortunately the 
> > > original post's title didn't mention OS X so it's not surprising that 
> > > nobody saw it. Glad to see that you guys are able to use them.
> > > 
> > 
> > Homage to you, sir!  Homage!
> > 
> > I've just successfully tested a simple multi-file Hello World in C++.
> > Coercing XCode to work with the cross-compiler was a bit tedious.  There is 
> > an O'Reilly book on embedded development with XCode but it's got some big 
> > errors in the setup procedure.  Most net references to environment 
> > variables show them in $(SOME_VARIABLE) form but the parenthesis are wrong. 
> >  They all need to be $SOME_VARIABLE.  I also had trouble with target names 
> > that had a space in them.  Usually you can put quotes around the path but 
> > that didn't work and I figured I could live without spaces.
> > 
> > Then linking was troublesome.  If you try to use a Build Rule to do it as 
> > the O'Reilly book suggests you end up explicitly entering each .o file 
> > which I thought was dumb and could cause one to tear hair out if they add a 
> > new file to the project down the road and forget to edit that rule.  Plus I 
> > think the rule gets executed for every .o file instead of once for the 
> > whole lot of them.  So I tried adding a Build Phase to run a script which 
> > would contain the linker command and a *.o input.  This works but you need 
> > to have a dummy Build Rule for *.o so the regular XCode linker doesn't get 
> > called.
> > 
> > Once I'm sure all this stuff works, I plan on posting the disk image files 
> > and a sample XCode project with all the rules and phases.
> > 
> > Now if I could figure out remote debugging....
> > And maybe I'll get ambitious and try building a whole Debian system.
> > 
> > Part of why I'm doing this is to try to compile the latest FTDI driver so I 
> > may tackle that one too.
> >
>




------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/ts-7000/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/ts-7000/join
    (Yahoo! ID required)

<*> To change settings via email:
     
    

<*> To unsubscribe from this group, send an email to:
    

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

<Prev in Thread] Current Thread [Next in Thread>
Admin

Disclaimer: Neither Andrew Taylor nor the University of NSW School of Computer and Engineering take any responsibility for the contents of this archive. It is purely a compilation of material sent by many people to the birding-aus mailing list. It has not been checked for accuracy nor its content verified in any way. If you wish to get material removed from the archive or have other queries about the archive e-mail Andrew Taylor at this address: andrewt@cse.unsw.EDU.AU