View Single Post
Old 04-29-2012, 11:20 PM   #21
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by knc1 View Post
There are differences between building a user application(s) and the building of an entire system from scratch.

Readers of this thread should keep that in mind when wondering why the differences in the suggestions you read here.

The suggestions you choose to follow depend on the task you intend to accomplish, not a matter of "the right way" or "the wrong way" - just different ways for different goals.
When building full apps that have library dependencies, cross compiling gets a LOT more complicated. When building kernel modules (device drivers and such), you not only need to link to the correct library versions, but you may also need to compile with the same version of gcc as was used to build the kernel. Installing multiple versions of CodeSourcery complicates using an IDE to run it. Supporting multiple kindle models gets difficult.

Because I want programs that work on all eink kindles, I tend to avoid library and header file dependencies when I can.

Even trying to install stuff that was already compiled correctly can be difficult when you have all kinds of version conflicts and missing dependencies while using apt-get.

Just when you think you have it mostly figured out, new problems crop up. Simple demos are fun and easy, but full complex systems start falling apart if you are using the wrong build tools.

In the end, there really is no RIGHT way or WRONG way. When I mention such things, I tend to use them humorously (in quotes, followed by a "grin" icon ). What is important is that what you create does the job you need it to do, regardless of WHAT tools you used to make it. If you were so inclined, you could even make /bin/sh do framebuffer graphics, despite the fact that C can be so much faster. As it turns out, I have gotten request to do more "eink algorithmic art" demos, which are claimed to be more "fun" than C programming. If doing graphics with /bin/sh, hexdump and dd is not using the "wrong" tools for the job, I do not know what could be worse (except perhaps using a dull spoon to do heart surgery).


Last edited by geekmaster; 04-29-2012 at 11:29 PM.
geekmaster is offline   Reply With Quote