Quote:
Originally Posted by knc1
Less than a 100mb system is relatively easy, special purpose systems less than 10mb are possible.
|
A good first step for new developers is to install my tcc package (which I will update with the missing eink header files).
When ready to go to the next step, it would be much better to use a small loop mount with a minimal gcc build environment that does much better code optimization (as suggested by
knc1) so you can compile programs that run much faster than those compiled with tcc.
But running the CodeSourcery cross-compiler is faster and better than either of the above methods, but requires that you "scp" the compiled file(s) over to the kindle to test them (unless you add that to the CodeBlocks compile). I have CodeSourcery installed in the CodeBlocks IDE in both my Linux Mint (Ubuntu-based debian distro), and in my Windows XP. It was easy to setup on both systems. I suppose that *somebody* should write some instructions on how to install CodeSourcery into CodeBlocks on both systems.
I like to write the preliminary code using CodeBlocks, and then for interactive debugging, the edit/compile/test sequence is much faster using tcc running on the kindle in an interactive session (where I use the nano editor). Then after debugging, you can "scp" the revised source code out of the kindle and back into the CodeBlocks project folder. Then release a final package with a fast binary that was cross-compiled with CodeSourcery.
