Hi all,
I'm looking for a fast way for developing a program in OE. In this
specific case, the program is a kdrive driver for a new graphic device
(the ATI Imageon).
Right now I'm doing this:
1) Build the unmodified package with OE.
2) Add my files, and modify the various configure.in and Makefile.am
(xserver-kdrive uses autotools)
3) bitbake -c configure -f xserver-kdrive.bb
4) bitbake -c compile -f xserver-kdrive.bb
5) copy the ipk to the handheld (I'm usually using scp over wireless net
for this)
6) Test the program
If, as it always is the case, the program has bugs, I modify the sources
again, then instead of running the compile command in OE, I just cd in
the source tree and manually run "make" from there, and the copy the row
executable file into the handheld. This is much faster. :-)
My problem is with debugging. I installed gdb in the handheld, and run
remotely "gdb myprogram" from a SSH session. But obviously, gdb cannot
find the source files in the handheld, because I never copied them
there. :-)
So, I would make a shell script for copying to the handheld all the
(modified) source files together with the executable, but I'm wondering
if there can be some better solution.
One could be install gcc in the handheld itself (it's a Zaurus C860) and
do all development "on site", but I would rather avoid it, since my
desktop PC is much faster. :-)
Anyone has better solutions? Unfortunately this is not a kind of program
I can test in my PC itself, since it's a graphic driver specific to the
Zaurus hardware...
Looking forward for any hints. :-)
--
Saluti,
Mardy
http://interlingua.altervista.org
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
_______________________________________________
Oe mailing list
Oe@handhelds.org
https://www.handhelds.org/mailman/listinfo/oe
