Quote:
Originally Posted by zxczxc
- - - -
You say you think knc1's idea of using qemu is better, why I don't understand why.
I want to build some code for kindle, but I'm not sure which method to follow.
I really appreciate it, thank you!
|
Partly it is subjective, partly technical.
There is code and then there is code.
Many software projects include test routines.
Running under an emulated environment lets you do the "make test" or "make check" that is supplied with the code.
You can't do that in a cross-compile environment.
Combining the techniques of qemu-static and a chroot - -
Then you can native build, including the install steps, (using "DESTDIR" argument) without fear of over-writing your host's version of the files.
If your dead set on using a cross-compile build environment - -
Use Buildroot(.org) - if they don't already have in the build tree what you want - you can easily add it.
The Buildroot build environment is high-quality, used by commercial embedded development (and developers).
Of course, you can do both -
Have Buildroot turn out a tar-ball of your stuff and everything else that it is dependent on.
Then populate a qemu-static, chroot with that tar-ball and test the hell out of (without risking your Kindle (yet) ).