Just looking at the configuration settings you can see that there are different
flavors of ARM processor. No idea if the iPhone ARM is the same (as far as the
compiler is concerned) as the Cirrus chips. Might be worth a look.
Personally, I want to A) build a cross-compiler that uses the latest & greatest
version of Linux and libc. Yann sent me an e-mail:
"I almost gave up on using glibc. I'm mostly using uClibc or eglibc.
Those two ones are easier to work with, because:
- glibc requires the ports addon to support ARM, some PPC, etc...
- glibc ports addon starting with 2.8 is no longer available as a tarball,
and requires either cvs or git snapshots
- using cvs/git means it's almost impossible to re-do the exact same
toolchain in the future
- eglibc uses svn, and that's easier to work with than cvs or git
- uClibc uses no addon at all, so a single download gets it all
But now uClibc has also switched to using git, I guess it's time that
crostool-NG knows about git retrieval... Sigh. I abhor git... :-("
Beyond that I want to build a complete Linux 2.6 system and get it running on
the 7260. Sure, my app runs fine under 2.4 but I want the following:
1) USB sound support (via a Turtle Beach or something cheaper)
2) I want fast boot and power-loss tolerant off the SD card which means EXT3 or
something else.
3) iNotify so I can more easily tell my app that a USB device has been plugged
in.
4) Better timer support.
5) A date with Julianne Hough but I don't see that happening any time soon
either.
--- In "tachion0niohcat" <> wrote:
>
> 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 "roberto.milani@" <milaniroberto@> 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/
|