Development environment for Microsoft Windows, featuring IDE, C compiler, debugger, resource editor and other utilities.
lcc-win64
Development environment for Microsoft Windows on AMD64 compatible processors, featuring IDE, C compiler, debugger, and other utilities.
lcc-win64 now available as free download
Dear lcc-win friends. Finally it's available for you as free update for non-professional use.
Get to the downloads and fetch your copy of lcc-win64 today Lcc-win64 status
It's now in a usable state product bug still under heavy development. The following works: The compiler and linker can be compiled with itself, and are capable of building wedit64 also The lcc-linux64 compiler is in production use. However lcc-win64 is more advanced, especially regarding to optimization Around 550 test files for the core compiler can be compiled and executed successfull
However there are a few trouble-spots: A fully new implemented C runtime library. Currently our wide char support is near non-existant. And it's not thread safe. Ports of diverse libraries still to be done No building of shared libraries No structures exception handlign Not all the examples have been ported
Especially the C runtime library is a hard problem. As you might know Microsoft does not provide a modern C runtime library any longer. You should use their .NET implementation.
Of course they provide a runtime library with their development environment, but to our best knowlege they do not permit to distribute it. But we have worked on facilities to enable it's use it. There's a flag you can set which will not use our library but Microsofts. You will probably have need for this to get access to a multithreading safe C runtime library.
AFAWK there is not 64-bit runtime library for any of the free compilers available. And you can check yourself, Microsoft has deprecated ! all C library functions in their new VC2005 development environment. You'll find hints to the Win32 API in there current Platform SDK, of course they can not drop that for the forseeable future. But they can underdocument this stuff, so you'll be left ot a trial-and-error approach to find out how things might (or might not work). But the base line is: Microsoft wants you to drop C completely.
Our opinion to C is quite a bit different, as you can imagine. Dropping C is not an alternative for us, and I bet for few hundred thousands others also. We do like C and you can blame C for a lot of things, but hardly for breaking existing code.
So our task is not a simple one. We have to provide the base infra-structure for you to enable further use of C on Windows.
