On Wed, Jul 23, 2008 at 4:04 PM, Lauri Leukkunen <[EMAIL PROTECTED]> wrote: > > On Jul 23, 2008, at 16:31 PM, E Robertson wrote: >>> >>> Most likely, unless people have fallen in love with SB1 and don't want to >>> give up their chroot jail. Stockholm syndrome. SB1 costs about 10x more >>> to >>> develop and maintain. >> >> Actually, I have for some time now but recently been having some >> problems using my custom toolchain (or foreign toolchain as they put >> it). >> It's been something I'm working on off and on but it's been giving me >> a beating. I do agree the maintainance is a problem but change takes >> time. >> I have to admit I took a look at OE and have been impressed with the >> way things are done in it. But I still like SB. > > I'm not going to get into "but SB is not a distro, like OE is" argument. :) > With SB2 there is no "native toolchain" vs. "foreign toolchain", anything > goes as is, with no modifications. As long as the gcc version is from this > decade. For older ones I cannot guarantee, but I suspect even they'll work. > >>>> - Scratchbox2 has nothing to do with Scratchbox. >>> >>> Not true. SB2 will be used by Nokia to replace SB1 at some point, it >>> seems >>> to take quite long to happen though, not surprisingly. >>> >>> >>>> - The Debian tools platforms stands on its own and can be used for >>>> development. >>> >>> Again I don't understand what you mean with "debian tools platform". >> >> Maybe refering to emdebian or debian cross tools? Which is a different >> environment that SB. > > In that case I'd say that SB2 complements them, there is overlap, but it's > all down to how the SDK is put together. It's just one more tool in the bag, > nothing more, nothing less. > >>> Most people who use SB (the people doing maemo work), got their >>> instructions >>> from their SDK provider (maemo.org in most cases). >>> >>> The sad state of the documentation on scratchbox.org reflects this. As >>> for >>> SB2, I've not cared about documentation myself. If someone wants to step >>> forward and start writing it into the fdo wiki, I'll promise to answer >>> *any* >>> question, more or less. :) >> >> Maybe many haven't switch to SB2 yet? like me :-). > > Probably, one of the big obstacles for developing SB2 is that most of its > potential users are using SB1 in their day jobs, they don't seem to have > time nor interest in experimenting with new ways. Funny how easily open > source is turned into a stagnated gray corporate playground.. All it takes > is a little money, and *poof*, there went all the fun.
So is there any strategy to resume the fun? One of the biggest problem with SB2 as I see it is lack of documentation that really describes it (especially the differences) wrt SB1. I wouldn't mind helping in this area if I understood more of it. Unfortunately, It was only until I took a look at OE that I realize what SB2 was trying to do, less the toolchain ( by the way, the last time I checked CodeSourcery toolchain didn't support uClibc). What little documentation is has is focused on Maemo and I've never used this SDK because from what I've seen it's too bulky. Maybe soon I'll be motivated to take another stab at SB2. _______________________________________________ Scratchbox-users mailing list [email protected] http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
