Thread: ct-ng is moving rapidly on, how do we keep it useful?
View Single Post
Old 10-20-2013, 07:47 PM   #29
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by idoit View Post
Thanks knc1.
Wish I knew this yesterday man! I didn't realize ct-ng is dead!!! Recent version seems really recent! 2013-10-02
Yesterday, I opted for ct-ng instead of exactly Buildroot!!! Buildroot is backed up by ulibC? And it uses ct-ng too.

Thanks NiLuJe, spent long hours on building ct-ng, I guess I'll keep it. Question is: I used the sample arm-unknown-linux-gnueabi. That'll do for Kindle (esp. Kindle 3 in mind) right?
Part of the removal of the old "back end" toolchain feature from Buildroot was the conversion of the toolchain generation into true "packages".

Currently only three (with one more a "WIP") uClibc, glibc and eglibc toolchains can be selected.

Yann does do 'bug fixing' as time is available, but that is expected (by Yann) to become less and less over time.
(I am paraphrasing Yann comments over time on the BR mailing list.)
knc1 is offline   Reply With Quote