On Wed, 27 Sep 2000, Russell Nelson wrote:
> Here are the reasons why compiled applications are [currently]
> difficult to develop on the iPAQ (maybe other platforms won't have
> these problems):
>
> o Cross-compilation requires installing an entire toolchain above
> and beyond the one you've got, plus you still have to copy files.
You can get RPMS of the cross-tool chain; it doesn't eat up too much
diskspace and it works (mostly) as you expect x86 gcc, etc to work. I am
not sure what "copy files" you're referring to, but you'll most certainly
have to copy any executable you produce onto your target(iPaq).
> I think that the best way to make compilation more easy and convenient
> to everyone with an iPAQ is to make the USB interface work well.
Agreed that transferring 2MB+ files via serial would be slow, but you can
use CF or a CF Ethernet card. I wonder if there's a hack to do 4Mbit IrDA
w/o all the silly IrDA stacks ("simple" serial program and z-modem or
something)...
At anyrate it shouldn't be too hard to get the cross-toolchain and start
doing stuff with it. And if you're really concerned about program size,
I'm sure you could link with Newlib instead of glibc though getting Newlib
cross-compiled isn't fun...
Unless you're doing driver level stuff or things that would really make an
ARM throw up, cross-compiling is great, write you code on your PC, test it
and just change the compiler name and voila, an ARM executable =).
Vasant.
Received on Wed Sep 27 14:41:53 2000
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:42:17 EDT