[geekmaster]

I tested my hello.c built with the PXA255 toolchain (supposedly compatible with the K1), and it ran fine in my K5. So it I *can* compile code that works on the K1, perhaps it will also work on later kindles without recompiling? I hope so... But then I will need to recompile ALL the hacks I want to support, so they can run on "all the kindles"...

So, yeah, now I need to learn enough ins and outs about "compiler flags", eh? I never had these problems on windows, though I was fond of building everything with vc6 for win98 (so it would work on "all the windows boxen")...

Time to find the LOWEST COMMON DENOMINATOR toolchain that can support all the kindles (with the exception of kernel modules, which I also plan to build when I have *time* to get compatible toolchains working for each specific kernel version, and with all the right flags and options set)...

I am not a happy camper right now, and I am not getting an younger burning time trying unsuccessfully to build apps from source. Even COBOL was easier than THIS! And yes, some of my COBOL programs were dynamically loading tcclib.dll (to be compliant with LGPL), and they used tcc to compile and run C scripts (used as search filters). Even that was easier than this...

But at least now I have a toolchain that I can use to compile my kindle video player (with sound support). I want gmplay to support the K1 2-bit video as well (4 pixels per byte). When I have time, I want to try pumping sound out the accessory port pads on the bottom of most kindles, and also perhaps out the power LEDs. A photocell connected to amplified speakers would not be so bad, for kindle sound, would it? But the accessory power pads can drive an LED reading light, so they ought to be able to drive a small speaker or headphones, I think...