Mercurial > hg > tinycc
view www/index.html @ 568:429a12b22806
Update web page to mention release.
author | Rob Landley <rob@landley.net> |
---|---|
date | Wed, 12 Mar 2008 00:14:36 -0500 |
parents | 9c9498a615ef |
children |
line wrap: on
line source
<!--#include file="header.html" --> <title>Tiny C Compiler</title> <h2><b>News</b></h2> <h2><b>March 11, 2008</b></h2> <p>Ok, it's been long enough that if I'm not ready for another full release, I'll at least knock out a -pre2. However, I've decided that enough development is going on that I'm going to call the next full release 1.0.0, and put out a few more pre releases as I close in on that.</p> <p>Here's the link to download <a href=downloads/tinycc-1.0.0-pre2.tar.bz2>tinycc-1.0.0-pre2</a>.</p> <p>The i386 and arm targets should work, with both gcc and uClibc. Neither win32 host nor target works, that's for -pre3. There's also a <a href=todo.txt>todo list</a> (which may not make sense to anybody but me, but there it is) outlining some of the steps on the way to 1.0.0.</p> <p>Ping <a href=/mailman/listinfo/tinycc>the list</a> if you have questions...</p> <h2><b>December 10, 2007</b></h2> <p>You can now download <a href=downloads/tinycc-0.9.25-pre1.tar.bz2>tinycc-0.9.25-pre1</a>. Run "make/make.sh" to build it, "make/test.sh" to test it, and "make/install.sh" (as root) to install it. Currently only the i386 target is enabled, I plan to poke at ARM next, and win32 if I can get Wine to like me. (If somebody would tell me how to test c67, I'd be more interested in supporting it. I haven't got one, or an emulator for it.)</p> <p>The actual 0.9.25 release is still scheduled for the end of the month.</p> <h2><b>November 14, 2007</b></h2> <p>There's a new <a href=http://landley.net/mailman/listinfo/tinycc>mailing list</a> for the project, a new build system, a new <a href=http://landley.net/hg/tinycc/file/tip/README>README</a>, and lots of changes to <a href=http://landley.net/hg/tinycc>the code</a>. My laptop now has 64-bit Ubuntu installed on it, so I'm working on getting it ready on an x86-64 host. I'm also redoing the build system, and doing several code cleanups I've been putting off because I'd be restructuring someone else's project.</p> <p>I'm aiming to have a release out by the end of the year. For more info, see the mailing list.</p> <h2><b>October 27, 2007</b></h2> <p>Started new project. Ok, I've been working on this darn unofficial fork on and off for a year, and it's time to decide if I'm doing it or not. I'm doing it.</p> <p>I'm making my fork (tinycc) a separate project from the original (tcc). I'm taking advantage of LGPL clause 3 to change the license of tinycc to GPL version 2. I'm poking around in mailman trying to set up a list for the new project.</p> <p>My goal is to get this thing to build everything Firmware Linux needs. That means it should build the Linux kernel, uClibc, and busybox/toybox. And, of course, itself.</p> <p>There's still a _lot_ of work left to be done, but that's just a matter of doing it.</p> <a href=old-news.html>Click here for older news.</a> <hr> <h2><b>About</b></h2> <p>This is a small, simple, and fast single pass C compiler. It produces executable code directly from C source, with no intermediate steps. It understands almost all of the C99 standard, plus several extensions from gcc.</p> <p>Tinycc can produce ELF executables (and .o files, and shared libraries) for x86, arm, and c67 processors. It can also run C code directly, as a scripting language, via the "#!/usr/bin/tinycc -run" construct.</p> <p>Tinycc already builds a working version of itself. The current goal is to implement enough features to build an unmodified Linux kernel, uClibc, and BusyBox (or toybox) to create a small self-bootstrapping Linux system in only four packages. (See the <a href=/code/firmware>Firmware Linux</a> project for details.)</p> <!--#include file="footer.html" -->