earlc8451 at clarkstate.edu
Fri Feb 1 17:41:12 CET 2008
>>> "Mark Arvidson" <sagacis at gmail.com> 02/01/08 11:23 AM >>>
I found the toolchain to be very easy to use. Unzip the .bz2 file,
run 'source /usr/local/openmoko/arm/setup-env' and you are set.
I keep my neo connected during development and ssh -X to it. That
way, I can scp the built binary over and run the program on my desktop
monitor but use the neo device processor and environment.
If you are writing appd that should work on your gnome desktop (i.e.
no gps or gsm), you can ./configure the Makefile for your local
desktop during developme, then om-conf when you sre ready to test on
On 2/1/08, john <jptmoore at gmail.com> wrote:
> Yes, you could have a simple shell script to setup your cross
> compilation toolchain. For example I use:
> . /etc/profile
> export OM=/home/john/moko
> export PATH=$OM/build/tmp/cross/arm-angstrom-linux-gnueabi/bin:$PATH
> echo "Type exit to leave cross compilation environment."
> On 01/02/2008, Christopher Earl <earlc8451 at clarkstate.edu> wrote:
> > Hope someone here can be of assistance. I want to develop apps for OM
> without using qemu or xoo or any of the other convoluted methods for
> application development. is there any easy way of developing apps on my
> desktop and compile it for OM, i was hoping that it would be simple gcc
> switches but I honestly have no idea. What is the easiest method used for
> application development.
> > _______________________________________________
> > OpenMoko community mailing list
> > community at lists.openmoko.org
> > http://lists.openmoko.org/mailman/listinfo/community
> OpenMoko community mailing list
> community at lists.openmoko.org
Sent from Gmail for mobile | mobile.google.com
OpenMoko community mailing list
community at lists.openmoko.org
More information about the community