--- In "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.
>
Just for everyone to know, a pretty simple way to build a cross compiler is to
just roll up all the files (more than you need, but hey, got plenty of disk
space) in /usr/lib /lib and /usr/include and then make this available to your
cross tool chain. This way you can link to all the libraries you have available
on your board. This method worked for me painlessly on both Linux and Mac OS X.
A description of it can be found here:
http://nuclear.unh.edu/wiki/index.php?title=ARM_Cross_Compiler
Cheers,
Tachion
------------------------------------
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/
|