On Fri, Jul 11, 2008 at 12:24 AM, Peter Bex <[EMAIL PROTECTED]> wrote: > I agree completely. Actually, I tend to view things in the opposite way: > WTF would anyone waste time trying to keep all those packages up-to-date, if > you can just install it using chicken-setup?
Because building them takes time. This has been my motivation for exploring cross-compilation: on my phone it takes several hours to compile chicken, and several more hours to compile the eggs I'm using. So when I'm short on time I spend more of it upgrading than actual development. I'm hoping that when OpenMoko is auto-generating new packages, and all I have to do to make that happen is visit the recipe(s) to increment the version number(s), the packages will indeed be fairly up-to-date, and it will only take a few minutes to install them. But on a real computer maybe it's a wash. An alternative idea: chicken-setup on the target could access a cache of pre-compiled eggs, on a server somewhere. If the server doesn't have it in the cache, then either the server can cross-compile it on behalf of the target machine, or the target could compile and upload it. (that depends on whether the server has the cross-toolchain or not) If the server always compiles, then once again the target does not need to have gcc, binutils, include files, dev libs etc. installed (which takes up more space than I have flash on the phone... which is why I have to run with an SD card to hold all the extra stuff) _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users