Kent A. Reed wrote: > Oops, I hit send too soon. > > Final question--- > > Are you compiling code natively on the BeagleBoard or cross-compiling on > a desktop machine? If cross-compiling, what tool chain are you using? > Right now, I'm doing all development and testing on PCs. But, for a deployed application using the Beagle, I did the development ON the Beagle, and it works fine. It may be marginally slower than an average PC, but not bad at all! This app has a couple page C program that creates a TCP server and then controls a signal multiplexer board using some GPIO pins. I think compiling and linking this code takes a couple seconds, tops.
I would think for this new app, I can just copy most of the files over from the PC (xxx.glade, xxx.py, xxx.c, etc.) and then just insert the OMAP GPIO-specific code before compiling there. This kernel is probably a bit dated now, but since I have made this GPIO mapping stuff work, I am loath to replace it without a good reason. Once the app is compiled, it becomes a single-purpose board used in a private network, so I'm not real concerned with having everything up to date. Torsten Koschorrek of RTAI got me to set up buildroot here to compile an RTAI-patched kernel, and I think I got it to run, but since I never had the RTAI patches, I never went very far with it. Jon ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
